Repository navigation
chore(ci): run the tests on python 3.12 to 3.15 - #138
Merged
Merged
Conversation
This file contains hidden or 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
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.
Proposed changes
The readme states that Python 3.12 or newer is supported, but CI only ran the tests on Python 3.15, so the tests now run on 3.12, 3.13, 3.14 and 3.15 without cancelling the other versions when one fails. While testing the versions locally, the UI test helper turned out to only check whether the tkinter module exists, so on systems where the module is present but the Tk library is missing the whole test run aborted during collection. The helper now imports tkinter and skips the UI tests if that fails, while REQUIRE_UI_TESTS=1 still turns this into an error in CI.
Types of changes
What types of changes does your code introduce to this project?
Put an
xin the boxes that apply