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.
19 `Black is beta <installation_and_usage.html#note-this-is-a-beta-product>`_.
25 **Dusty Phillips**, `writer <https://smile.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=dusty+phillips>`_:
27 *Black is opinionated so you don't have to be.*
29 **Hynek Schlawack**, creator of `attrs <http://www.attrs.org/>`_, core
30 developer of Twisted and CPython:
32 *An auto-formatter that doesn't suck is all I want for Xmas!*
34 **Carl Meyer**, `Django <https://www.djangoproject.com/>`_ core developer:
36 *At least the name is good.*
38 **Kenneth Reitz**, creator of `requests <http://python-requests.org/>`_
39 and `pipenv <https://docs.pipenv.org/>`_:
41 *This vastly improves the formatting of our code. Thanks a ton!*
49 installation_and_usage
52 version_control_integration
53 ignoring_unmodified_files
56 reference/reference_summary