-
-
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
Requirements output different since 2023.7.1 causing pip install issues #5777
Comments
timhourigan
added a commit
to timhourigan/pipenv
that referenced
this issue
Jul 4, 2023
timhourigan
added a commit
to timhourigan/pipenv
that referenced
this issue
Jul 4, 2023
2 tasks
timhourigan
added a commit
to timhourigan/pipenv
that referenced
this issue
Jul 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
The output of
pipenv requirements --hash
has changed slightly in2023.7.1
(#5757) andpip
appears to be sensitive to it in some scenarios, causingpip
to be unable to install the package(s) from the generated requirements.txt.Snippet of requirements.txt generated with
2023.6.26
Snippet of requirements.txt generated with
2023.7.1
- The hash is now before the markerExpected result
2023.7.1
generates a requirements.txt as per2023.6.26
Actual result
2023.7.1
generates a slightly different requirements.txtSteps to replicate
Pip successfully installs the package with the
2023.6.26
requirements.txt:Pip fails to install the package with the
2023.7.3
requirements.txt, thinking there is a hash mismatch even though it displays two identical shas:I will raise a PR with a fix for consideration.
The text was updated successfully, but these errors were encountered: