gh-131196: Improve uuid.__str__() performance a little more
#140663
+2
−1
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 PR follows up on the PR #131197 to further slightly (~2%) improve the performance of
UUID.__str__()by avoiding trampolining through thehexandbytesproperties.(Given that stringifying UUIDs is likely a pretty common use case, maybe this would be worth a speedup alternative in
_uuidmodule.c?)Here's what a
pytest-benchmarkcomparison says (suuidbeing a copy of thisuuid.pyandsuuid_origthe one from 3416e7c).Test code
```python import suuid_orig import suuid import pytest@pytest.mark.parametrize("module", [suuid, suuid_orig])
def test_suuid(benchmark, module):
u = module.uuid4()
def b():
assert str(u)
benchmark(b)