-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
gh-136599: Improve long_hash #136600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
eendebakpt
wants to merge
10
commits into
python:main
Choose a base branch
from
eendebakpt:long_hash
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
gh-136599: Improve long_hash #136600
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
146f5aa
Add test for long_hash
eendebakpt a162da2
Unroll first digit calculation in long_hash
eendebakpt 4f9fc76
Unroll second digit calculation in long_hash
eendebakpt 07bce4b
whitespace
eendebakpt 32341de
add gh number
eendebakpt 194fb7a
Merge branch 'long_hash' of github.com:eendebakpt/cpython into long_hash
eendebakpt a48860f
review comments
eendebakpt 6d3754b
fix test on wasi
eendebakpt fec9fbe
add news entry
eendebakpt 08d7ba9
review comments
eendebakpt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
1 change: 1 addition & 0 deletions
1
Misc/NEWS.d/next/Core_and_Builtins/2025-07-13-21-21-17.gh-issue-136599.sLhm2O.rst
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Improve performance of :class:`int` hash calculations. |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This assert will trigger for values like
hash(2**31)
for 32bit targets which use the default#define PYLONG_BITS_IN_DIGIT 30
cpython/Include/pyport.h
Lines 132 to 138 in 0d4fd10
because
cpython/Include/pyport.h
Line 170 in 0d4fd10
and thus
PyHASH_BITS
is 31cpython/Include/cpython/pyhash.h
Lines 12 to 18 in 0d4fd10
I suggest to add more tests to
test_long_hash
around these corner cases for such build configurations:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a check that
hash(-2**31)
is not-1
. For the others I has a bit hesitant as the values are implementation details (document as implementation details here: https://docs.python.org/3/library/stdtypes.html#hashing-of-numeric-types). To add tests I would have to get the (private) value ofPyHASH_MODULUS
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, your link also mentions that
PyHASH_MODULUS
is available via https://docs.python.org/3/library/sys.html#sys.hash_info.modulus, which is e.g. used incpython/Lib/test/test_numeric_tower.py
Line 14 in 283b050
and some other tests. But yeah, seems to be an implementation detail. Don't know for sure whether it's ok to use it in tests - but I think so?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PyHASH_MODULUS is not private anymore. And it was documented in the algorithm description before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "implementation details" are fully documented and
PyHASH_MODULUS
is indeed public. So I agree we need tests for the corner cases. I rewrote the tests to usesys.hash_info.modulus
.In
test_numeric_tower.py
there are more tests for the hash of ints, but these tests added here in this PR are not included there directly (only indirectly, e.g. by comparing the value ofhash(n)
withhash(float(n))
.