Bump peter-evans/create-or-update-comment from 2.1.1 to 3.0.1 (#3683)

[etc/vim.git] / docs / faq.md

diff --git a/docs/faq.md b/docs/faq.md
index aeb9634789f25fa4f2aeabd2748f8f0af1b81a6b..a6a422c2fece815b0605f390f7a563a5a288b291 100644 (file)
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -23,7 +23,7 @@ hooks, and scripting `unexpand` to run after applying _Black_.
 ## Does Black have an API?
 
 Not yet. _Black_ is fundamentally a command line tool. Many
 ## Does Black have an API?
 
 Not yet. _Black_ is fundamentally a command line tool. Many

-[integrations](integrations/index.rst) are provided, but a Python interface is not one
+[integrations](/integrations/index.md) are provided, but a Python interface is not one

 of them. A simple API is being [planned](https://github.com/psf/black/issues/779)
 though.
 
 of them. A simple API is being [planned](https://github.com/psf/black/issues/779)
 though.
 


@@ -39,7 +39,7 @@ other tools, such as `# noqa`, may be moved by _Black_. See below for more detai
 ## How stable is Black's style?
 
 Stable. _Black_ aims to enforce one style and one style only, with some room for
 ## How stable is Black's style?
 
 Stable. _Black_ aims to enforce one style and one style only, with some room for

-pragmatism. See [The Black Code Style](the_black_code_style/index.rst) for more details.
+pragmatism. See [The Black Code Style](the_black_code_style/index.md) for more details.

 
 Starting in 2022, the formatting output will be stable for the releases made in the same
 year (other than unintentional bugs). It is possible to opt-in to the latest formatting
 
 Starting in 2022, the formatting output will be stable for the releases made in the same
 year (other than unintentional bugs). It is possible to opt-in to the latest formatting


@@ -86,8 +86,8 @@ disabled-by-default counterpart W504. E203 should be disabled while changes are
 
 ## Which Python versions does Black support?
 
 
 ## Which Python versions does Black support?
 

-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
+Currently the runtime requires Python 3.7-3.11. Formatting is supported for files
+containing syntax from Python 3.3 to 3.11. 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.
 
 versions that have not reached their end of life. This is the case for both running
 _Black_ and formatting code.
 


@@ -95,6 +95,8 @@ Support for formatting Python 2 code was removed in version 22.0. While we've ma
 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.
 
 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.
 

+Runtime support for 3.6 was removed in version 22.10.0.
+

 ## Why does my linter or typechecker complain after I format my code?
 
 Some linters and other tools use magical comments (e.g., `# noqa`, `# type: ignore`) to
 ## Why does my linter or typechecker complain after I format my code?
 
 Some linters and other tools use magical comments (e.g., `# noqa`, `# type: ignore`) to