chore: drop old Python interpreters and update tooling #3028
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.
We had references to old versions of the Python interpreter, which most
certainly had security vulnerabilities and bugs and probably were not
used much.
If the users wish, they can include old versions by following our docs,
so this PR is about removing the old versions to make our CI faster. The
only thing that I am concerned is that we may be loosing our ability to
test what happens if we have multiple versions of the
3.X
toolchainregistered to ensure that we are resolving to the right interpreter.
Summary:
replica of the contents of the
TOOL_VERSIONS
which makes it easierto do bulk updates - just copy the output from the terminal and
cleanup unnecessary lines.
All of this work is to ensure that it is easier to test and add
pre-releases to catch regressions in the Python behaviour itself.