
I know I know, this is the second reorganization of the docs. I'm not saying the first one was bad or anything... but.. actually wait nah, *it was bad*. Anyway, welcome to probably my biggest commit. The main thing with this reorganization was to introduce nesting to the documentation! Having all of the docs be part of the main TOC was becoming too much. There wasn't much room to expand either. Finally, the old setup required a documentation generation step which was just annoying. The goals of this reorganization was to: 1. Significantly restructure the docs to be discoverable and understandable 2. Add room for further docs (like guides or contributing docs) 3. Get rid of the doc generation step (it was slow and frustrating) 4. Unblock other improvements and also just make contributing to the docs easier Another important change with this is that we are no longer using GitHub as a documentation host. While GitHub does support Markdown based docs actually pretty well, the lack of any features outside of GitHub Flavoured Markdown is quite limiting. ReadTheDocs is just much better suited for documentation. You can use reST, MyST, CommonMark, and all of their great features like toctrees and admonitions. Related to this change, we're adopting MyST as our flavour of Markdown. MyST introduces neat syntax extensions to Markdown that pretty much gives us the best of both worlds. The ease of use and simplicity of MD and the flexibility and expressiveness of reST. Also recommonmark is deprecated now. This switch was possible now we don't use GH as a docs host. MyST docs have to be built to really be usable / pretty, so the MD docs are going to look pretty bad on GH, but that's fine now! Another thing that should be noted is that the README has been stripped of most content since it was confusing. Users would read the README and then think some feature or bug was fixed already and is available in a release when in reality, they weren't. They were reading effectively the latest docs without knowing. See also: https://github.com/psf/black/issues/1759 FYI: CommonMark is a rationalized version of Markdown syntax -- Commit history before merge: * Switch to MyST-Parser + doc config cleanup recommonmark is being deprecated in favour of MyST-Parser. This change is welcomed, especially since MyST-Parser has syntax extensions for the Commonmark standard. Effectively we get to use a language that's powerful and expressive like ReST, but get the simplicity of Markdown. The rest of this effort will be using some MyST features. This reorganization efforts aims to remove as much duplication as possible. The regeneration step once needed is gone, significantly simplifing our Sphinx documentation configuration. * Tell pipenv we replaced recommonmark for MyST-Parser Also update `docs/requirements.txt` * Delete all auto generated content * Switch prettier for mdformat (plus a few plugins) **FYI: THIS WAS EFFECTIVELY REVERTED, SEE THIRD TO LAST COMMIT** prettier doesn't support MyST's syntax extensions which are going to be used in this reorganization effort so we have to switch formatter. Unfortanately mdformat's style is different from prettier's so time to reformat the whole repo too. We're excluding .github/ISSUE_TEMPLATE because I have no idea whether its changes are safe, so let's play it safe. * Fix the heading levels in CHANGES.md + a link MyST-Parser / sphinx's linkcheck complains otherwise. * Move reference docs into a docs/contributing dir They're for contributors of Black anyway. Also added a note in the summary document warning about the lack of attention the reference has been dealing with. * Rewrite and setup the new landing page + main TOC - add some more detail about Black's beta status - add licensing info - add external links in the main TOC for GitHub, PyPI, and IRC - prepare main TOC for new structure * Break out AUTHORS into its own file Not only was the AUTHORS list quite long, this makes it easy to include it in the Sphinx docs with just a simple symlink. * Add license to docs via a simple include Yes the document is orphaned but it is linked to in the landing page (docs/index.rst). * Add "The Black Code Style" section This mostly was a restructuring commit, there has been a few updates but not many. The main goal was to split "current style" and "planned changes to the style that haven't happened yet" to avoid confusion. * Add "Getting Started" page This is basically a quick start + even more. This commit is certainly one of most creatively involved in this effort. * Add "Usage and Configuration" section This commit was as much restructuring as new content. Instead of being in one giant file, usage and configuration documentation can expand without bloating a single file. * Add "Integrations" section Just a restructuring commit ... * Add "Guides" section This is a promising area of documentation that could easily grow in the future, let's prepare for that! * Add "Contributing" section This is also another area that I expect to see significant growth in. Contributors to Black could definitely do with some more specific docs that clears up certain parts of our slightly confusing project (it's only confusing because we're getting big and old!). * Rewrite CONTRIBUTING.md to just point to RTD * Rewrite README.md to delegate most info to RTD * Address feedback + a lot of corrections and edits I know I said I wanted to do these after landing this but given there's going to be no time between this being merged and a release getting pushed, I want these changes to make it in. - drop the number flag for mdformat - to reduce diffs, see also: https://mdformat.readthedocs.io/en/stable/users/style.html#ordered-lists - the GH issue templates should be safe by mdformat, so get rid of the exclude - clarify our configuration position - i.e. stop claiming we don't have many options, instead say we want as little formatting knobs as possible - lots and lots of punctuation, spelling, and grammar corrections (thanks Jelle!) - use RTD as the source for the CHANGELOG too - visual style cleanups - add docs about our .gitignore behaviour - expand GHA Action docs - clarify we want the PR number in the CHANGELOG entry - claify Black's behaviour for with statements post Python 3.9 - italicize a bunch of "Black"s Thank you goes to Jelle, Taneli (hukkinj1 on GH), Felix (felix-hilden on GH), and Wouter (wbolster on GH) for the feedback! * Merge remote-tracking branch 'upstream/master' into reorganize-docs-v2 merge conflicts suck, although these ones weren't too bad. * Add changelog entry + fix merge conflict resolution error I consider this important enough to be worthy of a changelog entry :) * Merge branch 'master' into reorganize-docs-v2 Co-authored-by: Łukasz Langa <lukasz@langa.pl> * Actually let's continue using prettier Prettier works fine for all of the default MyST syntax so let's not rock the boat as much. Dropping the mdformat commit was merge-conflict filled so here's additional commit instead. * Address Cooper's, Taneli's, and Jelle's feedback Lots of wording improvements by Cooper. Taneli suggested to disable the enabled by default MyST syntax not supported by Prettier and I agreed. And Jelle found one more spelling error! * More minor fixes
324 lines
9.4 KiB
Markdown
324 lines
9.4 KiB
Markdown
# Editor integration
|
|
|
|
## Emacs
|
|
|
|
Options include the following:
|
|
|
|
- [wbolster/emacs-python-black](https://github.com/wbolster/emacs-python-black)
|
|
- [proofit404/blacken](https://github.com/pythonic-emacs/blacken)
|
|
- [Elpy](https://github.com/jorgenschaefer/elpy).
|
|
|
|
## PyCharm/IntelliJ IDEA
|
|
|
|
1. Install `black`.
|
|
|
|
```console
|
|
$ pip install black
|
|
```
|
|
|
|
1. Locate your `black` installation folder.
|
|
|
|
On macOS / Linux / BSD:
|
|
|
|
```console
|
|
$ which black
|
|
/usr/local/bin/black # possible location
|
|
```
|
|
|
|
On Windows:
|
|
|
|
```console
|
|
$ where black
|
|
%LocalAppData%\Programs\Python\Python36-32\Scripts\black.exe # possible location
|
|
```
|
|
|
|
Note that if you are using a virtual environment detected by PyCharm, this is an
|
|
unneeded step. In this case the path to `black` is `$PyInterpreterDirectory$/black`.
|
|
|
|
1. Open External tools in PyCharm/IntelliJ IDEA
|
|
|
|
On macOS:
|
|
|
|
`PyCharm -> Preferences -> Tools -> External Tools`
|
|
|
|
On Windows / Linux / BSD:
|
|
|
|
`File -> Settings -> Tools -> External Tools`
|
|
|
|
1. Click the + icon to add a new external tool with the following values:
|
|
|
|
- Name: Black
|
|
- Description: Black is the uncompromising Python code formatter.
|
|
- Program: \<install_location_from_step_2>
|
|
- Arguments: `"$FilePath$"`
|
|
|
|
1. Format the currently opened file by selecting `Tools -> External Tools -> black`.
|
|
|
|
- Alternatively, you can set a keyboard shortcut by navigating to
|
|
`Preferences or Settings -> Keymap -> External Tools -> External Tools - Black`.
|
|
|
|
1. Optionally, run _Black_ on every file save:
|
|
|
|
1. Make sure you have the
|
|
[File Watchers](https://plugins.jetbrains.com/plugin/7177-file-watchers) plugin
|
|
installed.
|
|
1. Go to `Preferences or Settings -> Tools -> File Watchers` and click `+` to add a
|
|
new watcher:
|
|
- Name: Black
|
|
- File type: Python
|
|
- Scope: Project Files
|
|
- Program: \<install_location_from_step_2>
|
|
- Arguments: `$FilePath$`
|
|
- Output paths to refresh: `$FilePath$`
|
|
- Working directory: `$ProjectFileDir$`
|
|
|
|
- In Advanced Options
|
|
- Uncheck "Auto-save edited files to trigger the watcher"
|
|
- Uncheck "Trigger the watcher on external changes"
|
|
|
|
## Wing IDE
|
|
|
|
Wing supports black via the OS Commands tool, as explained in the Wing documentation on
|
|
[pep8 formatting](https://wingware.com/doc/edit/pep8). The detailed procedure is:
|
|
|
|
1. Install `black`.
|
|
|
|
```console
|
|
$ pip install black
|
|
```
|
|
|
|
1. Make sure it runs from the command line, e.g.
|
|
|
|
```console
|
|
$ black --help
|
|
```
|
|
|
|
1. In Wing IDE, activate the **OS Commands** panel and define the command **black** to
|
|
execute black on the currently selected file:
|
|
|
|
- Use the Tools -> OS Commands menu selection
|
|
- click on **+** in **OS Commands** -> New: Command line..
|
|
- Title: black
|
|
- Command Line: black %s
|
|
- I/O Encoding: Use Default
|
|
- Key Binding: F1
|
|
- [x] Raise OS Commands when executed
|
|
- [x] Auto-save files before execution
|
|
- [x] Line mode
|
|
|
|
1. Select a file in the editor and press **F1** , or whatever key binding you selected
|
|
in step 3, to reformat the file.
|
|
|
|
## Vim
|
|
|
|
### Official plugin
|
|
|
|
Commands and shortcuts:
|
|
|
|
- `:Black` to format the entire file (ranges not supported);
|
|
- `:BlackUpgrade` to upgrade _Black_ inside the virtualenv;
|
|
- `:BlackVersion` to get the current version of _Black_ inside the virtualenv.
|
|
|
|
Configuration:
|
|
|
|
- `g:black_fast` (defaults to `0`)
|
|
- `g:black_linelength` (defaults to `88`)
|
|
- `g:black_skip_string_normalization` (defaults to `0`)
|
|
- `g:black_virtualenv` (defaults to `~/.vim/black` or `~/.local/share/nvim/black`)
|
|
- `g:black_quiet` (defaults to `0`)
|
|
|
|
To install with [vim-plug](https://github.com/junegunn/vim-plug):
|
|
|
|
```
|
|
Plug 'psf/black', { 'branch': 'stable' }
|
|
```
|
|
|
|
or with [Vundle](https://github.com/VundleVim/Vundle.vim):
|
|
|
|
```
|
|
Plugin 'psf/black'
|
|
```
|
|
|
|
and execute the following in a terminal:
|
|
|
|
```console
|
|
$ cd ~/.vim/bundle/black
|
|
$ git checkout origin/stable -b stable
|
|
```
|
|
|
|
or you can copy the plugin from
|
|
[plugin/black.vim](https://github.com/psf/black/blob/stable/plugin/black.vim).
|
|
|
|
```
|
|
mkdir -p ~/.vim/pack/python/start/black/plugin
|
|
curl https://raw.githubusercontent.com/psf/black/stable/plugin/black.vim -o ~/.vim/pack/python/start/black/plugin/black.vim
|
|
```
|
|
|
|
Let me know if this requires any changes to work with Vim 8's builtin `packadd`, or
|
|
Pathogen, and so on.
|
|
|
|
This plugin **requires Vim 7.0+ built with Python 3.6+ support**. It needs Python 3.6 to
|
|
be able to run _Black_ inside the Vim process which is much faster than calling an
|
|
external command.
|
|
|
|
On first run, the plugin creates its own virtualenv using the right Python version and
|
|
automatically installs _Black_. You can upgrade it later by calling `:BlackUpgrade` and
|
|
restarting Vim.
|
|
|
|
If you need to do anything special to make your virtualenv work and install _Black_ (for
|
|
example you want to run a version from master), create a virtualenv manually and point
|
|
`g:black_virtualenv` to it. The plugin will use it.
|
|
|
|
To run _Black_ on save, add the following line to `.vimrc` or `init.vim`:
|
|
|
|
```
|
|
autocmd BufWritePre *.py execute ':Black'
|
|
```
|
|
|
|
To run _Black_ on a key press (e.g. F9 below), add this:
|
|
|
|
```
|
|
nnoremap <F9> :Black<CR>
|
|
```
|
|
|
|
**How to get Vim with Python 3.6?** On Ubuntu 17.10 Vim comes with Python 3.6 by
|
|
default. On macOS with Homebrew run: `brew install vim`. When building Vim from source,
|
|
use: `./configure --enable-python3interp=yes`. There's many guides online how to do
|
|
this.
|
|
|
|
**I get an import error when using _Black_ from a virtual environment**: If you get an
|
|
error message like this:
|
|
|
|
```text
|
|
Traceback (most recent call last):
|
|
File "<string>", line 63, in <module>
|
|
File "/home/gui/.vim/black/lib/python3.7/site-packages/black.py", line 45, in <module>
|
|
from typed_ast import ast3, ast27
|
|
File "/home/gui/.vim/black/lib/python3.7/site-packages/typed_ast/ast3.py", line 40, in <module>
|
|
from typed_ast import _ast3
|
|
ImportError: /home/gui/.vim/black/lib/python3.7/site-packages/typed_ast/_ast3.cpython-37m-x86_64-linux-gnu.so: undefined symbool: PyExc_KeyboardInterrupt
|
|
```
|
|
|
|
Then you need to install `typed_ast` and `regex` directly from the source code. The
|
|
error happens because `pip` will download [Python wheels](https://pythonwheels.com/) if
|
|
they are available. Python wheels are a new standard of distributing Python packages and
|
|
packages that have Cython and extensions written in C are already compiled, so the
|
|
installation is much more faster. The problem here is that somehow the Python
|
|
environment inside Vim does not match with those already compiled C extensions and these
|
|
kind of errors are the result. Luckily there is an easy fix: installing the packages
|
|
from the source code.
|
|
|
|
The two packages that cause the problem are:
|
|
|
|
- [regex](https://pypi.org/project/regex/)
|
|
- [typed-ast](https://pypi.org/project/typed-ast/)
|
|
|
|
Now remove those two packages:
|
|
|
|
```console
|
|
$ pip uninstall regex typed-ast -y
|
|
```
|
|
|
|
And now you can install them with:
|
|
|
|
```console
|
|
$ pip install --no-binary :all: regex typed-ast
|
|
```
|
|
|
|
The C extensions will be compiled and now Vim's Python environment will match. Note that
|
|
you need to have the GCC compiler and the Python development files installed (on
|
|
Ubuntu/Debian do `sudo apt-get install build-essential python3-dev`).
|
|
|
|
If you later want to update _Black_, you should do it like this:
|
|
|
|
```console
|
|
$ pip install -U black --no-binary regex,typed-ast
|
|
```
|
|
|
|
### With ALE
|
|
|
|
1. Install [`ale`](https://github.com/dense-analysis/ale)
|
|
|
|
1. Install `black`
|
|
|
|
1. Add this to your vimrc:
|
|
|
|
```vim
|
|
let g:ale_fixers = {}
|
|
let g:ale_fixers.python = ['black']
|
|
```
|
|
|
|
## Gedit
|
|
|
|
gedit is the default text editor of the GNOME, Unix like Operating Systems. Open gedit
|
|
as
|
|
|
|
```console
|
|
$ gedit <file_name>
|
|
```
|
|
|
|
1. `Go to edit > preferences > plugins`
|
|
1. Search for `external tools` and activate it.
|
|
1. In `Tools menu -> Manage external tools`
|
|
1. Add a new tool using `+` button.
|
|
1. Copy the below content to the code window.
|
|
|
|
```console
|
|
#!/bin/bash
|
|
Name=$GEDIT_CURRENT_DOCUMENT_NAME
|
|
black $Name
|
|
```
|
|
|
|
- Set a keyboard shortcut if you like, Ex. `ctrl-B`
|
|
- Save: `Nothing`
|
|
- Input: `Nothing`
|
|
- Output: `Display in bottom pane` if you like.
|
|
- Change the name of the tool if you like.
|
|
|
|
Use your keyboard shortcut or `Tools -> External Tools` to use your new tool. When you
|
|
close and reopen your File, _Black_ will be done with its job.
|
|
|
|
## Visual Studio Code
|
|
|
|
Use the
|
|
[Python extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python)
|
|
([instructions](https://code.visualstudio.com/docs/python/editing#_formatting)).
|
|
|
|
## SublimeText 3
|
|
|
|
Use [sublack plugin](https://github.com/jgirardet/sublack).
|
|
|
|
## Jupyter Notebook Magic
|
|
|
|
Use [blackcellmagic](https://github.com/csurfer/blackcellmagic).
|
|
|
|
## Python Language Server
|
|
|
|
If your editor supports the [Language Server Protocol](https://langserver.org/) (Atom,
|
|
Sublime Text, Visual Studio Code and many more), you can use the
|
|
[Python Language Server](https://github.com/palantir/python-language-server) with the
|
|
[pyls-black](https://github.com/rupert/pyls-black) plugin.
|
|
|
|
## Atom/Nuclide
|
|
|
|
Use [python-black](https://atom.io/packages/python-black) or
|
|
[formatters-python](https://atom.io/packages/formatters-python).
|
|
|
|
## Gradle (the build tool)
|
|
|
|
Use the [Spotless](https://github.com/diffplug/spotless/tree/main/plugin-gradle) plugin.
|
|
|
|
## Kakoune
|
|
|
|
Add the following hook to your kakrc, then run _Black_ with `:format`.
|
|
|
|
```
|
|
hook global WinSetOption filetype=python %{
|
|
set-option window formatcmd 'black -q -'
|
|
}
|
|
```
|
|
|
|
## Thonny
|
|
|
|
Use [Thonny-black-code-format](https://github.com/Franccisco/thonny-black-code-format).
|