Allow Python 3.13 #360
Closed
Allow Python 3.13 #360
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
|
@befeleme thanks for the pr :) If it's working, would it be possible for you to update the CI script, to also test for python 3.13? |
|
Bump on this, 3.13 was released a couple weeks ago and the Would you also consider removing the upper bound entirely? See https://iscinumpy.dev/post/bound-version-constraints/#pinning-the-python-version-is-special for a discussion on why the general recommendation is to leave it unbounded |
|
Hey @befeleme and @branchvincent #379 will superset this pr. |
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.
I've built pypandoc successfully with Python 3.13.0a5 in Fedora Linux 41 (and all the tests passed), so I think it could be good to relax the supported Python version range.