fix(bindings/python): remove greenlet benchmark dependencies - #8189
Merged
Conversation
Xuanwo
marked this pull request as ready for review
August 28, 2026 09:08
dosubot
Bot
added
size:M
PsiACE
approved these changes
Aug 28, 2026
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
2 participants
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.
Which issue does this PR close?
N/A.
Rationale for this change
The Python binding setup installs every dependency group. Its benchmark-only
greenifydependency uses CPython's Limited API, which is unsupported by free-threaded Python builds and preventsjust setupfrom completing when uv selects Python 3.14t.The Boto3 benchmark does not need an alternative I/O runtime. A bounded thread pool preserves its concurrent synchronous workload without coupling the binding development environment to gevent, greenlet, or greenify.
What changes are included in this PR?
Remove the greenlet-based benchmark dependencies and regenerate the uv lockfile. Replace the gevent benchmark with an asyncio-driven bounded thread pool, and update the benchmark commands and documentation.
Are there any user-facing changes?
There are no public API changes. Python binding development setup now works with free-threaded Python, and the Boto3 comparison benchmark uses threads instead of gevent greenlets.
AI Usage Statement
AI materially assisted with dependency analysis, implementation, and validation. The replacement preserves the concurrent workload shape, but no performance-equivalence claim is made because the S3 benchmark was not run against an actual service.