]>
git.madduck.net Git - etc/vim.git/blobdiff - docs/faq.md
madduck's git repository
Every one of the projects in this repository is available at the canonical
URL git://git.madduck.net/madduck/pub/<projectpath> — see
each project's metadata for the exact URL.
All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@ git. madduck. net .
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
SSH access, as well as push access can be individually
arranged .
If you use my repositories frequently, consider adding the following
snippet to ~/.gitconfig and using the third clone URL listed for each
project:
[url "git://git.madduck.net/madduck/"]
insteadOf = madduck:
## 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.
## 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
following will not be formatted:
- automagics (e.g. `pip install black`)
following will not be formatted:
- automagics (e.g. `pip install black`)
-- non-Python cell magics (e.g. `%%writelin e`). These can be added with the flag
- `--python-cell-magics`, e.g. `black --python-cell-magics writelin e hello.ipynb`.
+- non-Python cell magics (e.g. `%%writefil e`). These can be added with the flag
+ `--python-cell-magics`, e.g. `black --python-cell-magics writefil e hello.ipynb`.
- multiline magics, e.g.:
```python
- multiline magics, e.g.:
```python
## 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.
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
projects / etc / vim.git / blobdiff