actions/black
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Elaborate on Python support policy (#2819)

Browse Source
This commit is contained in:
Felix Hildén 2022-01-28 20:58:17 +02:00 committed by GitHub
parent 5f01b872e0
commit e1506769a4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
CHANGES.md
View File

@ -84,6 +84,7 @@ and the first release covered by our new stability policy.
- Change HTML theme to Furo primarily for its responsive design and mobile support
(#2793)
- Deprecate the `black-primer` tool (#2809)
- Document Python support policy (#2819)
## 21.12b0

11
docs/faq.md
View File

@ -71,9 +71,16 @@ readability because operators are misaligned. Disable W503 and enable the
disabled-by-default counterpart W504. E203 should be disabled while changes are still
[discussed](https://github.com/PyCQA/pycodestyle/issues/373).
## Does Black support Python 2?
## Which Python versions does Black support?
Support for formatting Python 2 code was removed in version 22.0.
Currently the runtime requires Python 3.6-3.10. Formatting is supported for files
containing syntax from Python 3.3 to 3.10. We promise to support at least all Python
versions that have not reached their end of life. This is the case for both running
_Black_ and formatting code.
Support for formatting Python 2 code was removed in version 22.0. While we've made no
plans to stop supporting older Python 3 minor versions immediately, their support might
also be removed some time in the future without a deprecation period.
## Why does my linter or typechecker complain after I format my code?