-
-
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 --update fails with SemVer violation #2063
Comments
The core issue is actually that this command sucks, which is why it hasn't existed since the |
SemVer and PEP 440 are inherently incompatible, so I don't know that you need to blame it on the command. 😄 |
Lol. Well I meant that the command should work irrespective of any semver compatibilities, we shouldn't have been doing a semver check there anyway. So I'm just glad that we axed it |
Sorry,I'm still confused.Thanks for any help.
My Error:
My understanding:
|
This command doesn’t work. We deleted it from pipenv. Please upgrade using pip, the same way you installed pipenv in the first place |
Thanks.
|
@NBR-hugh Pull requests welcomed! |
Running
pipenv --update
(with pipenv 9.0.0) fails with an error like the following:This is presumably due to the release of dev versions of v11.10.1 over the last few days. Multiple runs of the command will fail on different dev versions. (I believe the problem is that, according to SemVer spec item 9, pre-release data should be separated by a hyphen, not a dot; thus the above version should be
11.10.1-dev.5
.)The text was updated successfully, but these errors were encountered: