add FAQ entry about undetected syntax errors (#2645)
This came up in #2644.
This commit is contained in:
parent
e151686c6f
commit
ebd3e391da
@ -94,7 +94,14 @@ them in the right place, this detection is not and cannot be perfect. Therefore,
|
|||||||
sometimes have to manually move these comments to the right place after you format your
|
sometimes have to manually move these comments to the right place after you format your
|
||||||
codebase with _Black_.
|
codebase with _Black_.
|
||||||
|
|
||||||
## Can I run black with PyPy?
|
## Can I run Black with PyPy?
|
||||||
|
|
||||||
Yes, there is support for PyPy 3.7 and higher. You cannot format Python 2 files under
|
Yes, there is support for PyPy 3.7 and higher. You cannot format Python 2 files under
|
||||||
PyPy, because PyPy's inbuilt ast module does not support this.
|
PyPy, because PyPy's inbuilt ast module does not support this.
|
||||||
|
|
||||||
|
## Why does Black not detect syntax errors in my code?
|
||||||
|
|
||||||
|
_Black_ is an autoformatter, not a Python linter or interpreter. Detecting all syntax
|
||||||
|
errors is not a goal. It can format all code accepted by CPython (if you find an example
|
||||||
|
where that doesn't hold, please report a bug!), but it may also format some code that
|
||||||
|
CPython doesn't accept.
|
||||||
|
Loading…
Reference in New Issue
Block a user