Release v0.2.5 - #39
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.
This prepares winuvloop 0.2.5, a patch release focused on clean Python 3.14 imports and forward compatibility with Python 3.16's event-loop-policy removal.
Release notes
Fixed
winuvloopon Python 3.14 no longer eagerly resolves deprecated event-loop-policy APIs or emits anAbstractEventLoopPolicydeprecation warning.run()andnew_event_loop()remain clean under-W error::DeprecationWarning.installandEventLoopPolicycompatibility exports remain available through Python 3.15 and are removed from the public export list and typing declarations on Python 3.16+, matching uvloop and winloop.Compatibility and packaging
Requires-Python: >=3.8.1and the Python 3.14 classifier.There are no intentional breaking changes for supported APIs.
Verification
winuvloop.run().Publication
Merging this PR triggers the existing main-CI → version-tag → release workflow. It will create
v0.2.5, run cross-platform release smoke tests, publish to PyPI, and create the GitHub release.