-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update pip to 20.3.4/21.3.1 (new dependency resolver) #1259
Conversation
Update pip from 20.2.4 to: - 20.3.4 for Python 2.7 and 3.5 - 21.3.1 for Python 3.6+ Of note Pip 20.3+ includes the new dependency resolver (only enabled by default when using Python 3+). This new dependency resolver is more strict, see: https://pip.pypa.io/en/stable/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020 https://pip.pypa.io/en/stable/topics/dependency-resolution/ Release notes: https://pip.pypa.io/en/stable/news/#v21-3-1 Changelog: pypa/pip@20.2.4...21.3.1 The new versions of pip have been synced to S3 using: ``` $ pip download --no-cache pip==20.3.4 ... Saved ./pip-20.3.4-py2.py3-none-any.whl Successfully downloaded pip $ pip download --no-cache pip==21.3.1 Collecting pip==21.3.1 ... Saved ./pip-21.3.1-py3-none-any.whl Successfully downloaded pip $ aws s3 sync . s3://heroku-buildpack-python/common/ --exclude "*" --include "*.whl" --dryrun (dryrun) upload: ./pip-20.3.4-py2.py3-none-any.whl to s3://heroku-buildpack-python/common/pip-20.3.4-py2.py3-none-any.whl (dryrun) upload: ./pip-21.3.1-py3-none-any.whl to s3://heroku-buildpack-python/common/pip-21.3.1-py3-none-any.whl $ aws s3 sync . s3://heroku-buildpack-python/common/ --exclude "*" --include "*.whl" upload: ./pip-20.3.4-py2.py3-none-any.whl to s3://heroku-buildpack-python/common/pip-20.3.4-py2.py3-none-any.whl upload: ./pip-21.3.1-py3-none-any.whl to s3://heroku-buildpack-python/common/pip-21.3.1-py3-none-any.whl ``` Closes #1109. GUS-W-8493316.
Example of a new error shown when conflicting (invalid) dependency combinations are attempted to be installed:
I'll cover these in the changelog entry (the pip docs linked from the PR description explains how to resolve these). |
For apps that need a temporary workaround until you have time to fix the app's dependencies, you can pin to the previous version of the buildpack ( |
This reverts commit b82ddba. This was done to unblock Zenput deployments. See https://zenput.atlassian.net/browse/ZP-7880
Update pip from 20.2.4 to:
Of note Pip 20.3+ includes the new dependency resolver (only enabled by default when using Python 3+). This new dependency resolver is more strict, see:
https://pip.pypa.io/en/stable/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020
https://pip.pypa.io/en/stable/topics/dependency-resolution/
Release notes:
https://pip.pypa.io/en/stable/news/#v21-3-1
Changelog:
pypa/pip@20.2.4...21.3.1
The new versions of pip have been synced to S3 using:
Closes #1109.
GUS-W-8493316.