Add support for Python 3.13 and remove support for Python 3.9 #26
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
ruff reports zip-without-explicit-strict (B905) when iterables are not equal shapes. The fix is to add explicit keyword value.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for Python 3.13 and remove support for Python 3.9
This is a follow-up to Pull Request #23. Tests against Python 3.13 are mostly passing now (see below). The impact is that Python 3.9 support is removed. This is expected as Python 3.9 end-of-life is approaching this year.
Following the "Pull Request Guidelines"
Include an example for use
No core aspects were changed. One test was updated to reflect a recommendation from
ruff.Update the author list in AUTHORS.rst if applicable
Not applicable
Ensure that all checks passed (current checks include GitHub Actions)
Not all checks passed on my end again due to the frequently experienced TclError with Windows. While I have recommended add try-except with any doctest that calls matplotlib or to remove matplotlib in doctests altogether, I understand its impact on readability.
EDIT: Add some wording to reflect not all tests actually passed, but this is known and minor recurring problem.