Py313 #44
Merged
Py313 #44
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
metatoaster
force-pushed
the
py313
branch
2 times, most recently
from
59e61b0 to
29f7034
Compare
- While dropping Python 2.7 build support by default, because underlying tooling have largely moved on also and that I don't have time nor care to do further Python development, due to the amount of churn that will just break your old stuff with no recourse.
- Why the difference in behavior on the different platforms.
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.
Dropping support for building under Python 2.7.
Given that this package is unlikely to receive further development, lack of release for Python 2 is unlikely to be any hindrance to anyone. If I am going to do a future release I am probably going to wrap some library built with Rust and bring it over via PyO3 and call it a day.