-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Fix internal error on list/dict comprehension with walrus operator in global scope #9062
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
JelleZijlstra
merged 6 commits into
python:master
from
dhood:walrus_comprehension_global_bugfix
Aug 4, 2020
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e66891f
Add tests for dicts using assignment expression
dhood c0f633f
Duplicate walrus dict/list tests to global scope (passing)
dhood 822813d
Duplicate walrus comprehension tests to global scope (now failing)
dhood ed9ba4f
Use global symbol table if 1st non-comprehension scope
dhood a68bd68
Confirm the symbol table retrieved is not None
dhood 8585a4f
Add tests for assignment expression in class scope
dhood 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
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.
If reviewers are wondering why I didn't just use
d.items()
here instead of the list of tuples, it's because it's causingerror: "Dict[str, int]" has no attribute "items"
.I couldn't figure out why that was happening, I tried different flags and casting and whatnot but something in the test environment must be different... in a regular python script
filtered_dict = {k: new_v for k, v in d.items() if (new_v := v + 1) == 2}
can have its type revealed without such an error. Open to suggestions if you have ideas what's causing 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.
This is almost certainly because the test fixture you're using happens not to define
dict.items
. What you're doing here is fine.