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.
1 # Black as a server (blackd)
3 `blackd` is a small HTTP server that exposes _Black_'s functionality over a simple
4 protocol. The main benefit of using it is to avoid the cost of starting up a new _Black_
5 process every time you want to blacken a file.
9 `blackd` is not packaged alongside _Black_ by default because it has additional
10 dependencies. You will need to execute `pip install 'black[d]'` to install it.
12 You can start the server on the default port, binding only to the local interface by
13 running `blackd`. You will see a single line mentioning the server's version, and the
14 host and port it's listening on. `blackd` will then print an access log similar to most
15 web servers on standard output, merged with any exception traces caused by invalid
18 `blackd` provides even less options than _Black_. You can see them by running
21 ```{program-output} blackd --help
25 There is no official `blackd` client tool (yet!). You can test that blackd is working
29 blackd --bind-port 9090 & # or let blackd choose a port
30 curl -s -XPOST "localhost:9090" -d "print('valid')"
35 `blackd` only accepts `POST` requests at the `/` path. The body of the request should
36 contain the python source code to be formatted, encoded according to the `charset` field
37 in the `Content-Type` request header. If no `charset` is specified, `blackd` assumes
40 There are a few HTTP headers that control how the source code is formatted. These
41 correspond to command line flags for _Black_. There is one exception to this:
42 `X-Protocol-Version` which if present, should have the value `1`, otherwise the request
43 is rejected with `HTTP 501` (Not Implemented).
45 The headers controlling how source code is formatted are:
47 - `X-Line-Length`: corresponds to the `--line-length` command line flag.
48 - `X-Skip-String-Normalization`: corresponds to the `--skip-string-normalization`
49 command line flag. If present and its value is not the empty string, no string
50 normalization will be performed.
51 - `X-Skip-Magic-Trailing-Comma`: corresponds to the `--skip-magic-trailing-comma`
52 command line flag. If present and its value is not the empty string, trailing commas
53 will not be used as a reason to split lines.
54 - `X-Fast-Or-Safe`: if set to `fast`, `blackd` will act as _Black_ does when passed the
55 `--fast` command line flag.
56 - `X-Python-Variant`: if set to `pyi`, `blackd` will act as _Black_ does when passed the
57 `--pyi` command line flag. Otherwise, its value must correspond to a Python version or
58 a set of comma-separated Python versions, optionally prefixed with `py`. For example,
59 to request code that is compatible with Python 3.5 and 3.6, set the header to
61 - `X-Diff`: corresponds to the `--diff` command line flag. If present, a diff of the
62 formats will be output.
64 If any of these headers are set to invalid values, `blackd` returns a `HTTP 400` error
65 response, mentioning the name of the problematic header in the message body.
67 Apart from the above, `blackd` can produce the following response codes:
69 - `HTTP 204`: If the input is already well-formatted. The response body is empty.
70 - `HTTP 200`: If formatting was needed on the input. The response body contains the
71 blackened Python code, and the `Content-Type` header is set accordingly.
72 - `HTTP 400`: If the input contains a syntax error. Details of the error are returned in
74 - `HTTP 500`: If there was any other kind of error while trying to format the input. The
75 response body contains a textual representation of the error.
77 The response headers include a `X-Black-Version` header containing the version of