Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leading zero not parsed correctly when using new resolver in 20.3b1 #9093

Closed
QuicksilverMachine opened this issue Nov 3, 2020 · 1 comment

Comments

@QuicksilverMachine
Copy link

When using the 20.3b1 version, the following command fails:
pip install unidecode==0.04.21

It seems the leading zero in Unidecode's version (0.04.21) might be causing a problem.

ERROR: Exception:
Traceback (most recent call last):
  File "/Users/dejan/.pyenv/versions/3.9.0/envs/testing/lib/python3.9/site-packages/pip/_vendor/resolvelib/resolvers.py", line 186, in _merge_into_criterion
    crit = self.state.criteria[name]
KeyError: 'unidecode'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
...
  File "/Users/dejan/.pyenv/versions/3.9.0/envs/testing/lib/python3.9/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 286, in __init__
    assert str(version) == wheel.version, (
AssertionError: <Version('0.4.21')> != '0.04.21' for wheel unidecode```
@xavfernandez
Copy link
Member

Hello, thanks for the report.

It appears to be a duplicate of #9083 and should indeed be fixed in master thanks to #9085.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants