gh-142527: Docs: Clarify that random.seed() discards the sign of an integer input#142483
Merged
hauntsaninja merged 3 commits intopython:mainfrom Dec 19, 2025
Merged
gh-142527: Docs: Clarify that random.seed() discards the sign of an integer input#142483hauntsaninja merged 3 commits intopython:mainfrom
hauntsaninja merged 3 commits intopython:mainfrom
Conversation
If *a* is an integer, the sign of *a* is discarded in the C source code. Clarify this behavior to prevent foot guns, where a common use case might naively assume that flipping the sign will produce different sequences (e.g. for a train/test split of a synthetic data generator in machine learning).
AA-Turner
approved these changes
Dec 10, 2025
Member
AA-Turner
left a comment
There was a problem hiding this comment.
Indeed:
cpython/Modules/_randommodule.c
Line 321 in 4629567
The current wording is fine, though I think it could be a little shorter (see suggestion). Will leave to @rhettinger to decide.
A
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
hauntsaninja
approved these changes
Dec 19, 2025
Contributor
hauntsaninja
left a comment
There was a problem hiding this comment.
Thanks for the PR! (and Adam, for the edit)
It's been ten days, so I'm going to go ahead and merge
|
Thanks @karpathy for the PR, and @hauntsaninja for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Dec 19, 2025
…f an integer input (pythonGH-142483) If *a* is an integer, the sign of *a* is discarded in the C source code. Clarify this behavior to prevent foot guns, where a common use case might naively assume that flipping the sign will produce different sequences (e.g. for a train/test split of a synthetic data generator in machine learning). (cherry picked from commit 610aabf) Co-authored-by: Andrej <andrej.karpathy@gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Dec 19, 2025
…f an integer input (pythonGH-142483) If *a* is an integer, the sign of *a* is discarded in the C source code. Clarify this behavior to prevent foot guns, where a common use case might naively assume that flipping the sign will produce different sequences (e.g. for a train/test split of a synthetic data generator in machine learning). (cherry picked from commit 610aabf) Co-authored-by: Andrej <andrej.karpathy@gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
|
GH-142970 is a backport of this pull request to the 3.14 branch. |
|
GH-142971 is a backport of this pull request to the 3.13 branch. |
hauntsaninja
pushed a commit
that referenced
this pull request
Dec 19, 2025
…of an integer input (GH-142483) (#142970) gh-142527: Docs: Clarify that random.seed() discards the sign of an integer input (GH-142483) If *a* is an integer, the sign of *a* is discarded in the C source code. Clarify this behavior to prevent foot guns, where a common use case might naively assume that flipping the sign will produce different sequences (e.g. for a train/test split of a synthetic data generator in machine learning). (cherry picked from commit 610aabf) Co-authored-by: Andrej <andrej.karpathy@gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
hauntsaninja
pushed a commit
that referenced
this pull request
Dec 19, 2025
…of an integer input (GH-142483) (#142971) gh-142527: Docs: Clarify that random.seed() discards the sign of an integer input (GH-142483) If *a* is an integer, the sign of *a* is discarded in the C source code. Clarify this behavior to prevent foot guns, where a common use case might naively assume that flipping the sign will produce different sequences (e.g. for a train/test split of a synthetic data generator in machine learning). (cherry picked from commit 610aabf) Co-authored-by: Andrej <andrej.karpathy@gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
cocolato
pushed a commit
to cocolato/cpython
that referenced
this pull request
Dec 22, 2025
…f an integer input (python#142483) If *a* is an integer, the sign of *a* is discarded in the C source code. Clarify this behavior to prevent foot guns, where a common use case might naively assume that flipping the sign will produce different sequences (e.g. for a train/test split of a synthetic data generator in machine learning). Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
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.
If a is an integer, the sign of a is discarded in the C source code. Clarify this behavior to prevent foot guns, where a common use case might naively assume that flipping the sign will produce different sequences (e.g. for a train/test split of a synthetic data generator in machine learning).
A bit more context appears in this tweet, where I was surprised by this behavior, which led to a subtle bug that caused the train and test splits to be identical in a synthetic data generation task.
📚 Documentation preview 📚: https://cpython-previews--142483.org.readthedocs.build/