Thanks to visit codestin.com
Credit goes to github.com

Skip to content

chore: drop old Python interpreters and update tooling #3028

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

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Jun 25, 2025

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 toolchain
registered to ensure that we are resolving to the right interpreter.

Summary:

  • Remove old versions.
  • Update the tooling to format the printed text to be the exact
    replica of the contents of the TOOL_VERSIONS which makes it easier
    to do bulk updates - just copy the output from the terminal and
    cleanup unnecessary lines.
  • Document in the Changelog.
  • Use the latest python-build-standalone toolchain release.

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.

aignas added 8 commits June 25, 2025 17:33
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` toolchain
registered to ensure that we are resolving to the right interpreter.

Summary:
- [x] Remove old versions.
- [x] Update the tooling to format the printed text to be the exact
  replica of the contents of the `TOOL_VERSIONS` which makes it easier
  to do bulk updates - just copy the output from the terminal and
  cleanup unnecessary lines.
- [x] Document in the Changelog.
- [x] Use the latest python-build-standalone toolchain release.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant