Closed ssbarnea closed 1 year ago
The problem happens with 0.9.9
and 0.9.8
versions, but i was able to install 0.9.7
without problems. Clearly the project needs a test which validates that package is installable with pip 9.0.1
(even if not even older than this).
Thanks a lot for your report!
I changed to use setup.cfg since 0.9.8 and it might cause the problem. I'll dig into it this weekend.
@ssato Anychance of solving this? I keep getting into conflicts where Anyconfig 0.9.9 gets installed and breaks even when I mentioned anyconfig==0.9.7
, the last one that had a valid metadata.
I'm not sure this issue was resolved but tried that and uploaded the 0.9.10. Could you please try it?
@ssbarnea Can you still reproduce this with anyconfig 0.9.10?
pip3 install anyconfig
fails with:This is happening with pip 9.0.3, which happens to be the default version installed on the new
rhel8
.Package metadata should be adapted so installation failure does not happen, even if pip is not the latest and greatest.
What makes this problem even worse is that if user attempts to upgrade pip with pip, it will rended pip unusable:
This happens because pip installs exec into
/usr/local/bin/pip3
but system has it under/usr/bin/pip3
and the shim script uses an old import method which crashes the old launcher.Even afther finding workarounds to run with latest pip (19.2.1), I still get the same error.