Skip to content

Should we report col offset in some tokenizer errors? #110

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

Closed
pablogsal opened this issue Apr 21, 2020 · 3 comments
Closed

Should we report col offset in some tokenizer errors? #110

pablogsal opened this issue Apr 21, 2020 · 3 comments

Comments

@pablogsal
Copy link

./python 
Python 3.9.0a5+ (heads/more_errors:54e6bc98a7, Apr 21 2020, 03:55:06) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> def f():
...     pass
...   pass
  File "<stdin>", line 3
IndentationError: unindent does not match any outer indentation level
╰─ ./python -X oldparser
Python 3.9.0a5+ (heads/more_errors:54e6bc98a7, Apr 21 2020, 03:55:06) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> def f():
...     pass
...   pass
  File "<stdin>", line 3
    pass
       ^
IndentationError: unindent does not match any outer indentation level

Originally posted by @lysnikolaou in #105 (comment)

@ammaraskar
Copy link

Let's merge this with #121 which is being worked on by @isidentical

@lysnikolaou
Copy link
Member

Yup, this will probably be resolved once the fix for #121 is merged.

@lysnikolaou
Copy link
Member

Fixed in python#19782.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants