-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
gh-93476: Fraction.limit_denominator speed increase #93477
Closed
Closed
Changes from 3 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
599c55b
gh-93476: Fraction.limit_denominator speed increases
mscuthbert 70ca7ad
add NEWS.d item
mscuthbert a1a4fc8
Fix boundary case.
mscuthbert 3c06ded
Review comments
mscuthbert e5ab32e
trailing space
mscuthbert 40cbe78
return Fraction(self) for limit case
mscuthbert f5daa21
drop comment for now. can be separate PR
mscuthbert 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 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
2 changes: 2 additions & 0 deletions
2
Misc/NEWS.d/next/Library/2022-06-03-11-17-49.gh-issue-93476.vvjcGL.rst
This file contains 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,2 @@ | ||
:meth:`fractions.Fraction.limit_denominator()` performance enhancements. | ||
Patch by Michael Scott Asato Cuthbert. |
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.
Does this change make a significant difference to performance? If not, I'd suggest reverting it, both for readability and for the purposes of keeping the PR focused. From looking at the code, a simple
Fraction(self)
shouldn't end up doing any gcd calculation here.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.
It actually saves 30% on this case based on tests above -- however, I hadn't realized at the time that the
return self
was executed in this branch and no normalization was done. The speed increase is probably based on theisinstance()
check, which just keeps getting faster and faster in subsequent versions, so it might eventually be the faster route. I've removed the change.If Fractions are eventually to be truly immutable and hashable, then
return self
is the correct response here, but that is probably backwards incompatible with real code where people change_numerator
or_denominator
after instantiation.