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.
5 Options include the following:
7 - [purcell/reformatter.el](https://github.com/purcell/reformatter.el)
8 - [proofit404/blacken](https://github.com/pythonic-emacs/blacken)
9 - [Elpy](https://github.com/jorgenschaefer/elpy).
11 ## PyCharm/IntelliJ IDEA
19 2. Locate your `black` installation folder.
21 On macOS / Linux / BSD:
25 /usr/local/bin/black # possible location
32 %LocalAppData%\Programs\Python\Python36-32\Scripts\black.exe # possible location
35 Note that if you are using a virtual environment detected by PyCharm, this is an
36 unneeded step. In this case the path to `black` is `$PyInterpreterDirectory$/black`.
38 3. Open External tools in PyCharm/IntelliJ IDEA
42 `PyCharm -> Preferences -> Tools -> External Tools`
44 On Windows / Linux / BSD:
46 `File -> Settings -> Tools -> External Tools`
48 4. Click the + icon to add a new external tool with the following values:
51 - Description: Black is the uncompromising Python code formatter.
52 - Program: <install_location_from_step_2>
53 - Arguments: `"$FilePath$"`
55 5. Format the currently opened file by selecting `Tools -> External Tools -> black`.
57 - Alternatively, you can set a keyboard shortcut by navigating to
58 `Preferences or Settings -> Keymap -> External Tools -> External Tools - Black`.
60 6. Optionally, run _Black_ on every file save:
62 1. Make sure you have the
63 [File Watchers](https://plugins.jetbrains.com/plugin/7177-file-watchers) plugin
65 2. Go to `Preferences or Settings -> Tools -> File Watchers` and click `+` to add a
69 - Scope: Project Files
70 - Program: <install_location_from_step_2>
71 - Arguments: `$FilePath$`
72 - Output paths to refresh: `$FilePath$`
73 - Working directory: `$ProjectFileDir$`
76 - Uncheck "Auto-save edited files to trigger the watcher"
77 - Uncheck "Trigger the watcher on external changes"
81 Wing supports black via the OS Commands tool, as explained in the Wing documentation on
82 [pep8 formatting](https://wingware.com/doc/edit/pep8). The detailed procedure is:
90 2. Make sure it runs from the command line, e.g.
96 3. In Wing IDE, activate the **OS Commands** panel and define the command **black** to
97 execute black on the currently selected file:
99 - Use the Tools -> OS Commands menu selection
100 - click on **+** in **OS Commands** -> New: Command line..
102 - Command Line: black %s
103 - I/O Encoding: Use Default
105 - [x] Raise OS Commands when executed
106 - [x] Auto-save files before execution
109 4. Select a file in the editor and press **F1** , or whatever key binding you selected
110 in step 3, to reformat the file.
114 Commands and shortcuts:
116 - `:Black` to format the entire file (ranges not supported);
117 - `:BlackUpgrade` to upgrade _Black_ inside the virtualenv;
118 - `:BlackVersion` to get the current version of _Black_ inside the virtualenv.
122 - `g:black_fast` (defaults to `0`)
123 - `g:black_linelength` (defaults to `88`)
124 - `g:black_skip_string_normalization` (defaults to `0`)
125 - `g:black_virtualenv` (defaults to `~/.vim/black` or `~/.local/share/nvim/black`)
127 To install with [vim-plug](https://github.com/junegunn/vim-plug):
130 Plug 'psf/black', { 'branch': 'stable' }
133 or with [Vundle](https://github.com/VundleVim/Vundle.vim):
139 and execute the following in a terminal:
142 $ cd ~/.vim/bundle/black
143 $ git checkout origin/stable -b stable
146 or you can copy the plugin from
147 [plugin/black.vim](https://github.com/psf/black/blob/stable/plugin/black.vim).
150 mkdir -p ~/.vim/pack/python/start/black/plugin
151 curl https://raw.githubusercontent.com/psf/black/stable/plugin/black.vim -o ~/.vim/pack/python/start/black/plugin/black.vim
154 Let me know if this requires any changes to work with Vim 8's builtin `packadd`, or
157 This plugin **requires Vim 7.0+ built with Python 3.6+ support**. It needs Python 3.6 to
158 be able to run _Black_ inside the Vim process which is much faster than calling an
161 On first run, the plugin creates its own virtualenv using the right Python version and
162 automatically installs _Black_. You can upgrade it later by calling `:BlackUpgrade` and
165 If you need to do anything special to make your virtualenv work and install _Black_ (for
166 example you want to run a version from master), create a virtualenv manually and point
167 `g:black_virtualenv` to it. The plugin will use it.
169 To run _Black_ on save, add the following line to `.vimrc` or `init.vim`:
172 autocmd BufWritePre *.py execute ':Black'
175 To run _Black_ on a key press (e.g. F9 below), add this:
178 nnoremap <F9> :Black<CR>
181 **How to get Vim with Python 3.6?** On Ubuntu 17.10 Vim comes with Python 3.6 by
182 default. On macOS with Homebrew run: `brew install vim`. When building Vim from source,
183 use: `./configure --enable-python3interp=yes`. There's many guides online how to do
186 **I get an import error when using _Black_ from a virtual environment**: If you get an
187 error message like this:
190 Traceback (most recent call last):
191 File "<string>", line 63, in <module>
192 File "/home/gui/.vim/black/lib/python3.7/site-packages/black.py", line 45, in <module>
193 from typed_ast import ast3, ast27
194 File "/home/gui/.vim/black/lib/python3.7/site-packages/typed_ast/ast3.py", line 40, in <module>
195 from typed_ast import _ast3
196 ImportError: /home/gui/.vim/black/lib/python3.7/site-packages/typed_ast/_ast3.cpython-37m-x86_64-linux-gnu.so: undefined symbool: PyExc_KeyboardInterrupt
199 Then you need to install `typed_ast` and `regex` directly from the source code. The
200 error happens because `pip` will download [Python wheels](https://pythonwheels.com/) if
201 they are available. Python wheels are a new standard of distributing Python packages and
202 packages that have Cython and extensions written in C are already compiled, so the
203 installation is much more faster. The problem here is that somehow the Python
204 environment inside Vim does not match with those already compiled C extensions and these
205 kind of errors are the result. Luckily there is an easy fix: installing the packages
206 from the source code.
208 The two packages that cause the problem are:
210 - [regex](https://pypi.org/project/regex/)
211 - [typed-ast](https://pypi.org/project/typed-ast/)
213 Now remove those two packages:
216 $ pip uninstall regex typed-ast -y
219 And now you can install them with:
222 $ pip install --no-binary :all: regex typed-ast
225 The C extensions will be compiled and now Vim's Python environment will match. Note that
226 you need to have the GCC compiler and the Python development files installed (on
227 Ubuntu/Debian do `sudo apt-get install build-essential python3-dev`).
229 If you later want to update _Black_, you should do it like this:
232 $ pip install -U black --no-binary regex,typed-ast
235 ## Visual Studio Code
238 [Python extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python)
239 ([instructions](https://code.visualstudio.com/docs/python/editing#_formatting)).
243 Use [sublack plugin](https://github.com/jgirardet/sublack).
245 ## Jupyter Notebook Magic
247 Use [blackcellmagic](https://github.com/csurfer/blackcellmagic).
249 ## Python Language Server
251 If your editor supports the [Language Server Protocol](https://langserver.org/) (Atom,
252 Sublime Text, Visual Studio Code and many more), you can use the
253 [Python Language Server](https://github.com/palantir/python-language-server) with the
254 [pyls-black](https://github.com/rupert/pyls-black) plugin.
258 Use [python-black](https://atom.io/packages/python-black).
260 ## Gradle (the build tool)
262 Use the [Spotless](https://github.com/diffplug/spotless/tree/main/plugin-gradle) plugin.
266 Add the following hook to your kakrc, then run _Black_ with `:format`.
269 hook global WinSetOption filetype=python %{
270 set-option window formatcmd 'black -q -'
276 Use [Thonny-black-code-format](https://github.com/Franccisco/thonny-black-code-format).
278 ## Other integrations
280 Other editors and tools will require external contributions.
282 Patches welcome! ✨ 🍰 ✨
284 Any tool that can pipe code through _Black_ using its stdio mode (just
285 [use `-` as the file name](https://www.tldp.org/LDP/abs/html/special-chars.html#DASHREF2)).
286 The formatted code will be returned on stdout (unless `--check` was passed). _Black_
287 will still emit messages on stderr but that shouldn't affect your use case.
289 This can be used for example with PyCharm's or IntelliJ's
290 [File Watchers](https://www.jetbrains.com/help/pycharm/file-watchers.html).