Optimize zero-timeout Python receives for 3.0.2 - #68
Merged
Merged
Conversation
prezaei
force-pushed
the
codex/python-readme-postrelease
branch
from
September 18, 2026 05:42
459e5a7 to
10beaed
Compare
prezaei
changed the title
prezaei
changed the title
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
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.
Subscriber.receive(timeout=0)now uses the immediate receive path, avoiding GIL release/reacquisition and timer bookkeeping. The Rust implementation already skipped the OS wait for zero timeouts; Python signal handling and return values are preserved.Bump the synchronized native package versions to 3.0.2 using the existing release checks. The Python release will also include the corrected PyPI installation README.
Validation: built the release Python wheel with the locked Rust dependencies and ran the Python API tests against that installed wheel. Release version consistency checks pass. The previous CI run had a Windows failure in the existing Rust
notification_errors_preserve_committed_resultstest, before Python tests ran; this needs resolution before merge.