Moving py3.8 and python+prybar over to historical modules #397
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
In preparation for next month's EOL, opening an intent-to-deprecate PR so we can stop building python3.8.
Sphinx is not supported for python 3.8 and below, and while I cannot find it at this point, there is a long thread of people talking about how it's not worth trying to backport since 3.8 is so close to EOL.
What changed
Moving the
python-3.8module over to historical modules, deleting the module definition.Test plan
It should be possible to switch from our wrapped pip over to stock pip, which has been blocked by this sphinx issue.
Rollout