Specify FUTURE_PYTHON_VERSION as version range #218
Merged
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
mauritsvanrees
added a commit
to zopefoundation/zope.exceptions
that referenced
this pull request
Oct 11, 2023
This is a testing PR for zopefoundation/meta#218 It introduces Python hyphen ranges in `tests.yml` for the future Python 3.13. Manually added `3.11.0 - 3.11.2` to see the effect for a current Python. To make the code differences smaller, this branch is based on #30 which updated to latest meta three weeks ago.
mauritsvanrees
approved these changes
Oct 11, 2023
There was a problem hiding this comment.
I tried it out in zopefoundation/zope.exceptions#31 and the version ranges seem to work as intended.
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.
See https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#specifying-a-python-version and scroll down to
hyphen ranges: It's apparently possible to specify a range of versions for a Python version to be used with the GitHubsetup-pythonaction. That way we won't have to update this package for every new prerelease. It also means testing for the value ofFUTURE_PYTHON_VERSIONto determine ifwith_future_pythonhas to be set is no longer necessary. Only the package'sfuture-pythonsetting is considered.This is not fully tested because there's no Python 3.13 preprelease yet.