Use stable Python 3.11 in tests #641
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
|
There is a 3.12 dev release, maybe worth trying? Might be unstable, but would be good to start testing a version without distutils sooner rather than later? :) |
|
Here is a guide on how to set this up, including allowing the 3.12 to fail and still call the tests a success; https://pythontest.com/testing-with-python-3-12/#what-if-312-fails-but-i-dont-want-my-pipeline-to-stop |
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.
Since 3.11 has been out for a while now, the tests should probably use the latest stable instead of dev version.
Should the changes to remove the
-devsuffix for nox also be removed?Or keep that, but also add Python 3.12-dev to the tests? Configured in such a way that those tests are allowed to fail.