https://bugzilla.redhat.com/show_bug.cgi?id=1835934
Pavol Zacik <pzacik(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(jskarvad(a)redhat.c
| |om)
--- Comment #20 from Pavol Zacik <pzacik(a)redhat.com> ---
Python guidelines say that `pip install chirp` MUST install the same package or
nothing [1], which is not the case here [2]. I understand that the rule did not
exist when this package was first created. From the guidelines, it is not clear
what the correct procedure is in the case of a retired package, but it may be
one of the following:
- rename the package,
- ask for an exception,
- resolve this with Python SIG or PyPI.
When I run the chirp binary without arguments, it fails with the following
traceback:
```
Traceback (most recent call last):
File "/usr/bin/chirp", line 8, in <module>
sys.exit(chirpmain())
^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/chirp/wxui/__init__.py", line 65, in
chirpmain
import wx
ModuleNotFoundError: No module named 'wx'
```
It seems the wXPython dependency is somehow not generated correctly from
requirements.txt.
Lastly, I would add at least %doc README.chirpc under %files; it seems useful.
[1]
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_pypi_p...
[2]
https://pypi.org/project/chirp/
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=1835934
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...