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 documentation master file, created by
2 sphinx-quickstart on Fri Mar 23 10:53:30 2018.
4 The uncompromising code formatter
5 =================================
7 By using *Black*, you agree to cede control over minutiae of
8 hand-formatting. In return, *Black* gives you speed, determinism, and
9 freedom from `pycodestyle` nagging about formatting. You will save time
10 and mental energy for more important matters.
12 *Black* makes code review faster by producing the smallest diffs
13 possible. Blackened code looks the same regardless of the project
14 you're reading. Formatting becomes transparent after a while and you
15 can focus on the content instead.
17 Try it out now using the `Black Playground <https://black.vercel.app>`_.
19 .. admonition:: Note - this is a beta product
21 *Black* is already `successfully used <https://github.com/psf/black#used-by>`_ by
22 many projects, small and big. *Black* has a comprehensive test suite, with efficient
23 parallel tests, our own auto formatting and parallel Continuous Integration runner.
24 However, *Black* is still beta. Things will probably be wonky for a while. This is
25 made explicit by the "Beta" trove classifier, as well as by the "b" in the version
26 number. What this means for you is that **until the formatter becomes stable, you
27 should expect some formatting to change in the future**. That being said, no drastic
28 stylistic changes are planned, mostly responses to bug reports.
30 Also, as a safety measure which slows down processing, *Black* will check that the
31 reformatted code still produces a valid AST that is effectively equivalent to the
33 `Pragmatism <./the_black_code_style/current_style.html#pragmatism>`_
34 section for details). If you're feeling confident, use ``--fast``.
37 :doc:`Black is licensed under the MIT license <license>`.
42 **Mike Bayer**, author of `SQLAlchemy <https://www.sqlalchemy.org/>`_:
44 *I can't think of any single tool in my entire programming career that has given me a
45 bigger productivity increase by its introduction. I can now do refactorings in about
46 1% of the keystrokes that it would have taken me previously when we had no way for
47 code to format itself.*
49 **Dusty Phillips**, `writer <https://smile.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=dusty+phillips>`_:
51 *Black is opinionated so you don't have to be.*
53 **Hynek Schlawack**, creator of `attrs <https://www.attrs.org/>`_, core
54 developer of Twisted and CPython:
56 *An auto-formatter that doesn't suck is all I want for Xmas!*
58 **Carl Meyer**, `Django <https://www.djangoproject.com/>`_ core developer:
60 *At least the name is good.*
62 **Kenneth Reitz**, creator of `requests <http://python-requests.org/>`_
63 and `pipenv <https://docs.pipenv.org/>`_:
65 *This vastly improves the formatting of our code. Thanks a ton!*
71 Use the badge in your project's README.md:
75 [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
78 Using the badge in README.rst:
82 .. image:: https://img.shields.io/badge/code%20style-black-000000.svg
83 :target: https://github.com/psf/black
87 .. image:: https://img.shields.io/badge/code%20style-black-000000.svg
88 :target: https://github.com/psf/black
97 the_black_code_style/index
104 usage_and_configuration/index
120 GitHub ↪ <https://github.com/psf/black>
121 PyPI ↪ <https://pypi.org/project/black>
122 IRC ↪ <https://webchat.freenode.net/?channels=%23blackformatter>