Use fixed Python version for Python/PyPI installs #146
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
It is increasingly common for packages in the Python data space to have lagging support for the newest Python release. This means that we could periodically break due to new Python releases (see carpentriesoffline#143) and if a release happened right before a workshop that would be an issue. Therefore the safer approach with Python is to fix the version and then periodically test and update after new releases. This change sets the version to 3.12 and uses this version for all Python related installation.
ethanwhite
force-pushed
the
python-version-fixed
branch
from
1a04839 to
6b02b30
Compare
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.
It is increasingly common for packages in the Python data space to have
lagging support for the newest Python release.
This means that we could periodically break due to new Python releases
(see #143) and if a release happened right before a workshop that would
be an issue. Therefore the safer approach with Python is to fix the
version and then periodically test and update after new releases.
This change sets the version to 3.12 and uses this version for all
Python related installation.