]>
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:
still proposed on the issue tracker. See
[The Black Code Style](the_black_code_style/index.rst) for more details.
still proposed on the issue tracker. See
[The Black Code Style](the_black_code_style/index.rst) 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
+styles, using the `--future` flag.
+
## Why is my file not formatted?
Most likely because it is ignored in `.gitignore` or excluded with configuration. See
## Why is my file not formatted?
Most likely because it is ignored in `.gitignore` or excluded with configuration. See
get_ipython().system('ls')
```
get_ipython().system('ls')
```
-- invalid syntax, as it can't be safely distinguished from automagics in the absens e of
+- invalid syntax, as it can't be safely distinguished from automagics in the absenc e of
a running `IPython` kernel.
## Why are Flake8's E203 and W503 violated?
a running `IPython` kernel.
## Why are Flake8's E203 and W503 violated?
## Does Black support Python 2?
## Does Black support Python 2?
+```{warning}
+Python 2 support has been deprecated since 21.10b0.
+
+This support will be dropped in the first stable release, expected for January 2022.
+See [The Black Code Style](the_black_code_style/index.rst) for details.
+```
+
For formatting, yes! [Install](getting_started.md#installation) with the `python2` extra
For formatting, yes! [Install](getting_started.md#installation) with the `python2` extra
-to format Python 2 files too! There are no current plans to drop support, but most
-likely it is bound to happen. Sometime. Eventually. In terms of running _Black_ though,
-Python 3.6 or newer is required.
+to format Python 2 files too! In terms of running _Black_ though, Python 3.6 or newer is
+required.
## Why does my linter or typechecker complain after I format my code?
## Why does my linter or typechecker complain after I format my code?
them in the right place, this detection is not and cannot be perfect. Therefore, you'll
sometimes have to manually move these comments to the right place after you format your
codebase with _Black_.
them in the right place, this detection is not and cannot be perfect. Therefore, you'll
sometimes have to manually move these comments to the right place after you format your
codebase with _Black_.
+
+## Can I run black with PyPy?
+
+Yes, there is support for PyPy 3.7 and higher. You cannot format Python 2 files under
+PyPy, because PyPy's inbuilt ast module does not support this.