-
-
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
Support for python 3.6.0 broken due to pip bug in newly vendored version #5008
Comments
@mungojam Just noting that it was |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
We are hitting pypa/pip#10280 in the latest version of pipenv because it updated to a version that suffers from the bug (21.2.2). We need to use the latest version of pipenv in order to allow us to update to later versions of python using pyenv-win, so we're in a bit of a catch-22.
The bug was fixed in 21.2.4, so please could you release a patched version that uses this.
I see that you are planning on dropping 3.6 support in a later version (#4966), so I hope you can get this fix in before making that change.
Expected result
pipenv to work with 3.6.0 so that we can easily update our tools to later versions of python using recent pyenv-win fixes.
Actual result
pipenv is not usable due to the pip error happening when running
pipenv install
and I can't provide our team with a simple way to gradually update python across our tools using pyenv-win.The error is:
Steps to replicate
Hopefully not needed, I'm just hitting the bug listed in the pip issue above.
Sorry, it's got too much internal info in it, but hopefully you have enough to go on
The text was updated successfully, but these errors were encountered: