I found a temporary work-around by modifying PKG-INFO:Version 7.5.3-deb10u1 to: PKG-INFO:Version: 7.5.3 under reportbug's dist-packages directory, to match PEP 440 compliance of no dashes, etc. Successfully Installed my package and I can move on now.
I am not sure if this can help anyone or not and by far is definitely not the fix. Also, not sure of the ramifications of modifying the package version, but.......
Thank you guys for everything you do!
Hello Folks!I hope everyone is doing great today/tonight!We are experiencing an item with a package named "fairseq" and are experiencing the following symptoms:Running setup.py develop for fairseq
.........
.........
File "/tmp/pip-build-env-n1wx5a7x/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2631, in hashcmp
self.parsed_version,
File "/tmp/pip-build-env-n1wx5a7x/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2685, in parsed_version
raise packaging.version.InvalidVersion(f"{str(ex)} {info}") from None
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '7.5.3-deb10u1' (package: reportbug)
We have researched this and have been advised by the setuptools team to request you to please release a stable update with the fix from:Python versions like `11.6.0ubuntu1` or `7.5.3~deb10u1` are not PEP440 compliant. With setuptools 66, the versions of all packages visible in the Python environment *must* obey PEP440.We are actively looking for a work-around and I thought that I should report this item.Please let me know if you need any information from me?Any guidance is appreciated!Thank you,Matt