Elaborate on Python support policy (#2819)

diff --git a/CHANGES.md b/CHANGES.md
index f81c285d0beef8de895b5d211958345ebda64f0c..440aaeaa35a6245c89aecad0c9a3759d9d3536fa 100644 (file)
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -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
 

diff --git a/docs/faq.md b/docs/faq.md
index 0cff6ae5e1db27444760d3cb18f1274b336160db..264141e3f39c61b014ee6322e26ec59b4abebbf4 100644 (file)
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -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?