Control: tags -1 - moreinfo + confirmed Control: retitle -1 python3-coverage: Entry point error on some supported Python versions Control: found -1 python3-coverage/6.2+dfsg1-2 Control: summary -1 0
The upstream install script does not handle all Debian supported Python versions. This is caused by the hard-coding of only the default Python interpreter during installation of console scripts. The result is that any other Python version does not have a working entry point: $ python3-coverage --version Coverage.py, version 6.2 with C extension Full documentation is at https://coverage.readthedocs.io $ python3.9-coverage --version Coverage.py, version 6.2 with C extension Full documentation is at https://coverage.readthedocs.io $ python3.10-coverage --version Traceback (most recent call last): File "/usr/bin/python3.10-coverage", line 33, in <module> sys.exit(load_entry_point('coverage==6.2', 'console_scripts', 'python3.10-coverage')()) File "/usr/bin/python3.10-coverage", line 25, in importlib_load_entry_point return next(matches).load() StopIteration On 04-Apr-2020, Uwe Hermann wrote: > Adding the following line to > /usr/lib/python3/dist-packages/coverage-4.5.2.egg-info/entry_points.txt > seems to fix it: > > python3.8-coverage = coverage.cmdline:main That would get a command that runs, yes; but it does not specifically target Python 3.8 as intended. Instead, the installation procedure needs to be changed so that it specifically installs console scripts with each correct Python interpreter shebang line. -- \ “Earth gets its price for what Earth gives us.” —James Russell | `\ Lowell | _o__) | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature