Add warning about Python 3.13 on Windows. #426
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
mhsmith
reviewed
Oct 7, 2024
|
The RTD build is failing because of a broken link on git-scm.org. |
Dammit... I fixed that issue last week, but forgot to update my branch before forking for the PR. |
mhsmith
approved these changes
Oct 7, 2024
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.
Python 3.13.0 is imminent, but Python.net explicitly excludes 3.13 support because of a known crash (see pythonnet/pythonnet#2454).
When 3.13.0 is released, it will become the default download on python.org, so we need to get ahead of those users.
This doesn't affect Linux users, as the system Python won't be Python 3.13 anywhere for at least a couple of months (and even when it is, the PyGobject dependency can be compiled for 3.13); on macOS, Rubicon has been tested with 3.13.
PR Checklist: