-
-
Notifications
You must be signed in to change notification settings - Fork 32k
incorrect SyntaxError #109120
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
Labels
3.11
only security fixes
3.12
only security fixes
3.13
bugs and security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
topic-parser
type-bug
An unexpected behavior, bug, or error
Comments
Yeah, no changes in 3.12 and |
On 3.8 it used to be just:
|
grigoriev-semyon
added a commit
to grigoriev-semyon/cpython
that referenced
this issue
Apr 2, 2024
pablogsal
pushed a commit
that referenced
this issue
Apr 2, 2024
grigoriev-semyon
added a commit
to grigoriev-semyon/cpython
that referenced
this issue
Apr 2, 2024
…ssions (python#117444) (cherry picked from commit c97d3af)
grigoriev-semyon
added a commit
to grigoriev-semyon/cpython
that referenced
this issue
Apr 2, 2024
…ssions (python#117444) (cherry picked from commit c97d3af)
grigoriev-semyon
added a commit
to grigoriev-semyon/cpython
that referenced
this issue
Apr 2, 2024
…ssions (python#117444) (cherry picked from commit c97d3af)
Should the backports be merged? |
pablogsal
pushed a commit
that referenced
this issue
Apr 3, 2024
terryjreedy
pushed a commit
that referenced
this issue
Apr 4, 2024
diegorusso
pushed a commit
to diegorusso/cpython
that referenced
this issue
Apr 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3.11
only security fixes
3.12
only security fixes
3.13
bugs and security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
topic-parser
type-bug
An unexpected behavior, bug, or error
Bug report
Bug description:
The following input will cause a
SyntaxError
. That's all well and good, but the message for theSyntaxError
is incorrect.This is not correct. That error message is intended for cases like this
f(**kwargs, *args)
.This bug is present on
3.9
,3.10
, and3.11
. I haven't tested3.12
, but I suspect that it is present there as well. The bug is not present on3.8
.CPython versions tested on:
3.8 3.9, 3.10, 3.11
Operating systems tested on:
Linux, Windows
Linked PRs
The text was updated successfully, but these errors were encountered: