Skip to content

bpo-41659: Disallow curly brace directly after primary #22996

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.

Sign up for GitHub

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
lysnikolaou merged 4 commits into from
Oct 27, 2020
Merged

bpo-41659: Disallow curly brace directly after primary #22996

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8a12bf5
bpo-41659: Disallow curly brace directly after primary
lysnikolaou Oct 26, 2020
aada2f0
Add comment
lysnikolaou Oct 27, 2020
a4f3585
Add tests
lysnikolaou Oct 27, 2020
d73538a
📜🤖 Added by blurb_it.
blurb-it[bot] Oct 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
📜🤖 Added by blurb_it.
  • Loading branch information
@blurb-it
blurb-it[bot] authored Oct 27, 2020
commit d73538a6b2dac2c47cd80606f56d304d5382a5c6
3 changes: 3 additions & 0 deletions Misc/NEWS.d/next/Core and Builtins/2020-10-27-18-32-49.bpo-41659.d4a-8o.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
Fix a bug in the parser, where a curly brace following a `primary` didn't fail immediately.
This led to invalid expressions like `a {b}` to throw a :exc:`SyntaxError` with a wrong offset,
or invalid expressions ending with a curly brace like `a {` to not fail immediately in the REPL.