Skip to content

[BUG] Issue installing prospector #739

@robertalexa

Description

@robertalexa

Hi guys,

It seems all of a sudden that the installation of prospector fails with the following:

16.19   error: subprocess-exited-with-error
16.19   
16.19   × Getting requirements to build wheel did not run successfully.
16.19   │ exit code: 1
16.19   ╰─> [36 lines of output]
16.19       Warning: 'classifiers' should be a list, got type 'tuple'
16.19       Traceback (most recent call last):
16.19         File "/usr/local/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
16.19           main()
16.19           ~~~~^^
16.19         File "/usr/local/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
16.19           json_out['return_val'] = hook(**hook_input['kwargs'])
16.19                                    ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
16.19         File "/usr/local/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
16.19           return hook(config_settings)
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 334, in get_requires_for_build_wheel
16.19           return self._get_build_requires(config_settings, requirements=[])
16.19                  ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 304, in _get_build_requires
16.19           self.run_setup()
16.19           ~~~~~~~~~~~~~~^^
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 522, in run_setup
16.19           super().run_setup(setup_script=setup_script)
16.19           ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 320, in run_setup
16.19           exec(code, locals())
16.19           ~~~~^^^^^^^^^^^^^^^^
16.19         File "<string>", line 43, in <module>
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/_distutils/core.py", line 160, in setup
16.19           dist.parse_config_files()
16.19           ~~~~~~~~~~~~~~~~~~~~~~~^^
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/dist.py", line 730, in parse_config_files
16.19           self._parse_config_files(filenames=inifiles)
16.19           ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/dist.py", line 599, in _parse_config_files
16.19           opt = self._enforce_underscore(opt, section)
16.19         File "/tmp/pip-build-env-gqd24slh/overlay/lib/python3.13/site-packages/setuptools/dist.py", line 629, in _enforce_underscore
16.19           raise InvalidConfigError(
16.19           ...<3 lines>...
16.19           )
16.19       setuptools.errors.InvalidConfigError: Invalid dash-separated key 'description-file' in 'metadata' (setup.cfg), please use the underscore name 'description_file' instead.
16.19       [end of output]
16.19   
16.19   note: This error originates from a subprocess, and is likely not a problem with pip.
16.44 

This output show only the failing part. Worth mentioning that I have emptied out all other packages in requirements.txt which led me to prospector as the culprit. Everything has been working in the same configuration for a while (last tried building an image a few hours ago).

The install is happening in docker FROM --platform=linux/amd64 python:3.13.2-slim with prospector at 1.15.3

Can you guys give this a test at your end please? Happy to provide further info if instructed.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions