-
Notifications
You must be signed in to change notification settings - Fork 686
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
unpin the pip version #3859
Comments
Should we unpin this or should we keep pip version pinned so that future breakage in pipenv doesn't create a scramble? |
I'm fine with unpinning. At the very least, we should at least re-pin, meaning update pip fully, confirm no problems, and commit pin to the new latest. |
Unpinned in #5090, closing this ticket. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In PR #3853, we pinned the pip version to 18.0 to work around pypa/pipenv#2924. We need to roll this change back once a fix is out.
The text was updated successfully, but these errors were encountered: