-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-37723: fix performance regression on regular expression parsing #15030
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
Merged
serhiy-storchaka
merged 4 commits into
python:master
from
yannvgn:fix-sre-parsing-perf-regression
Jul 31, 2019
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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
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.
How about this?
Uh oh!
There was an error while loading. Please reload this page.
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.
Since
dict.fromkeys()
already jumbled up the item unless there's a need to return a list, returning a set might be more optimal when checking for unique, i.e.But it seems like the original
_uniq()
function returns a list. Is there a reason to do that?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.
set(dict.fromkeys(X))
is totally useless. When you needset
,set(X)
is enoguh.But in this case, we need list, not set. So I used
list(dict.fromkeys(X))
.Uh oh!
There was an error while loading. Please reload this page.
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.
We indeed need a list. And I guess that preserving the order is important, looking at the initial implementation.
I'm fine with
list(dict.fromkeys(items))
(and it's much prettier), but I have 2 minor concerns:list(dict.fromkeys(items))
might be a bit slower (though I didn't check, and the difference is negligible I think)What do you think?
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 believe
list(dict.fromkeys(items))
is significantly faster than[it for it in items if it not in seen or seen.add(it)]
You said "sre_parse._uniq function, which does not exist in Python <= 3.6."
So no need to think about 3.6.
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.
@methane you were right, list(dict.fromkeys(items)) seems to be a bit faster. Changed ✅.