Skip to content

A SyntaxError less detailed since 3.10 in specific example #94192

Closed

Description

@Serpens66

Python 3.10.5

New SyntaxError ^ pointer is misleading in following example compared to older python versions.

d = {
    "foo":"foo",
    "bar":lambda b:{"bar":testfn(von="1"b=b)}, 
    }

Results in error message on 3.10.5:

File "test.py", line 3
  "bar":lambda b:{"bar":testfn(von="1"b=b)},
       ^
SyntaxError: expression expected after dictionary key and ':'

While on python 3.8 it was more helpful:

File "test.py", line 3
  "bar":lambda b:{"bar":testfn(von="1"b=b)},
                                      ^
SyntaxError: invalid syntax

edit: added triple backquotes to preserve formatting on github. thanks hauntsaninja.
On 3.10.5 it is pointing on the ":" prior to lambda, while on 3.8 it is pointing on the missing comma.

Activity

  1. hauntsaninja commented on Jun 24, 2022

    @hauntsaninja
    Contributor

    You can use triple backquotes (```) to preserve formatting on Github.

    λ python3.9
    Python 3.9.12 (main, Apr 16 2022, 17:49:09) 
    [Clang 13.0.0 (clang-1300.0.27.3)] on darwin
    Type "help", "copyright", "credits" or "license" for more information.
    >>> d = { "foo":"foo", "bar":lambda b:{"bar":testfn(von="1"b=b)}, }
      File "<stdin>", line 1
        d = { "foo":"foo", "bar":lambda b:{"bar":testfn(von="1"b=b)}, }
                                                               ^
    SyntaxError: invalid syntax
    
    λ python3.10
    Python 3.10.5 (main, Jun 18 2022, 23:46:13) [Clang 13.0.0 (clang-1300.0.27.3)] on darwin
    Type "help", "copyright", "credits" or "license" for more information.
    >>> d = { "foo":"foo", "bar":lambda b:{"bar":testfn(von="1"b=b)}, }
      File "<stdin>", line 1
        d = { "foo":"foo", "bar":lambda b:{"bar":testfn(von="1"b=b)}, }
                                ^
    SyntaxError: expression expected after dictionary key and ':'
    
  2. iritkatriel commented on Jun 26, 2022

    @iritkatriel
    Member
  3. wookie184 commented on Jun 26, 2022

    @wookie184
    Contributor

    I think i've found a simple fix that seems to work, will open a PR.

  4. added a commit that references this issue on Jun 26, 2022
  5. added 2 commits that reference this issue on Jun 26, 2022
  6. added a commit that references this issue on Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    interpreter-core(Objects, Python, Grammar, and Parser dirs)type-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions