Use debug f-strings for feature detection (#3215)

[etc/vim.git] / docs / the_black_code_style / index.md

diff --git a/docs/the_black_code_style/index.md b/docs/the_black_code_style/index.md
index d1508552fee8311be2fc77776dd96fda71cfdaa3..c7f29af6c736125e41d218b8b9ee22deac5b10b4 100644 (file)
--- a/docs/the_black_code_style/index.md
+++ b/docs/the_black_code_style/index.md
@@ -24,13 +24,16 @@ below. Ongoing style considerations are tracked on GitHub with the
 The following policy applies for the _Black_ code style, in non pre-release versions of
 _Black_:
 
-- The same code, formatted with the same options, will produce the same output for all
-  releases in a given calendar year.
+- If code has been formatted with _Black_, it will remain unchanged when formatted with
+  the same options using any other release in the same calendar year.
 
-  This means projects can safely use `black ~= 22.0` without worrying about major
-  formatting changes disrupting their project in 2022. We may still fix bugs where
-  _Black_ crashes on some code, and make other improvements that do not affect
-  formatting.
+  This means projects can safely use `black ~= 22.0` without worrying about formatting
+  changes disrupting their project in 2022. We may still fix bugs where _Black_ crashes
+  on some code, and make other improvements that do not affect formatting.
+
+  In rare cases, we may make changes affecting code that has not been previously
+  formatted with _Black_. For example, we have had bugs where we accidentally removed
+  some comments. Such bugs can be fixed without breaking the stability policy.
 
 - The first release in a new calendar year _may_ contain formatting changes, although
   these will be minimised as much as possible. This is to allow for improved formatting