-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add test for A᧚ = 0
#1557
Labels
C: maintenance
Related to project maintenance, e.g. CI, testing, policy changes, releases
good first issue
Good for newcomers
Comments
Yapf has the same problem, google/yapf#403, |
Resolved by 5e2bb52 first available in 21.12b0 which broadened the acceptable character set for NAMES significantly. Thanks for reporting! |
We should add a regression test to make sure this doesn't regress if we change our tokenizer. |
ichard26
added
the
C: maintenance
Related to project maintenance, e.g. CI, testing, policy changes, releases
label
Dec 14, 2021
hauntsaninja
pushed a commit
to hauntsaninja/black
that referenced
this issue
Jan 28, 2022
Resolves psf#1557
hauntsaninja
pushed a commit
to hauntsaninja/black
that referenced
this issue
Jan 28, 2022
Resolves psf#1557
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C: maintenance
Related to project maintenance, e.g. CI, testing, policy changes, releases
good first issue
Good for newcomers
Black v19.10b0 fails to parse certain assignments involving unicode identifiers - playground link here.
This code is in fact valid Python, as you can confirm by pasting it into a repl or with
compile("A\u19da = 0")
.Found, as with most of my bugs, via Hypothesmith. Given that this applies to multiple unicode digit characters, it might be due to unicode digits in identifiers?
The text was updated successfully, but these errors were encountered: