Fix get-pip which dropped support for legacy Python #1793
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The usage of an f-string in
get-pip
breaks pyenv builds of Python 2.7, 3.4, and 3.5 until this PR (or similar) is landed and released. Fix pyenv to continue to support these legacy Python builds despite the fact thatget-pip
has dropped support for Python 2.7 as discussed in pypa/pip#9520 --> pypa/get-pip#87.Also, fix Python 3.4 and 3.5 which also do not support f-strings.
https://bootstrap.pypa.io/
Make sure you have checked all steps below.
Prerequisite
Description
Tests