-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
pipenv doesn't understand some version markers #1790
Comments
Did you manage to find what |
it is either the evaluation logic not handling this marker properly. or the logic that parses the markers (loaded from the coverage package) doesn't parse it correctly. |
@asherf I've typically seen errors pop up like this when there are conflicts between the installation path of pipenv and python (e.g. |
yep. that seems to be the case. |
No there wouldn't be, can you run |
@techalchemy sounds good. I'll try that. |
Sorry for the trouble & thanks for jumping through these hoops! |
@techalchemy the solution you suggested solved the problem... |
Pipenv fails to parse some python version markers
given this Pipfile:
when running pipenv internally runs resolver.py it fails because it is unable to properly parse the version markers of the coverage packages.
so given that Pipfile if I run
pipenv lock
it crashes (exit code 1) because resolver.py failshere is part of the output from running
pipenv lock --verbose
environment:
I tried to debug the issue, the code responsible for parsing the version markers is running under notpip
The text was updated successfully, but these errors were encountered: