X-Git-Url: https://git.madduck.net/etc/vim.git/blobdiff_plain/6027cca10d6c84363e63d20b961f837a046ad7ad..fda2561f79e10826dbdeb900b6124d642766229f:/docs/index.rst?ds=inline diff --git a/docs/index.rst b/docs/index.rst index fab9851..8a8da0d 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -4,6 +4,8 @@ The uncompromising code formatter ================================= + “Any color you like.” + By using *Black*, you agree to cede control over minutiae of hand-formatting. In return, *Black* gives you speed, determinism, and freedom from `pycodestyle` nagging about formatting. You will save time @@ -14,16 +16,36 @@ possible. Blackened code looks the same regardless of the project you're reading. Formatting becomes transparent after a while and you can focus on the content instead. -Try it out now using the `Black Playground `_. +Try it out now using the `Black Playground `_. -.. note:: +.. admonition:: Note - Black is now stable! - `Black is beta `_. + *Black* is `successfully used `_ by + many projects, small and big. *Black* has a comprehensive test suite, with efficient + parallel tests, our own auto formatting and parallel Continuous Integration runner. + Now that we have become stable, you should not expect large formatting to changes in + the future. Stylistic changes will mostly be responses to bug reports and support for new Python + syntax. + Also, as a safety measure which slows down processing, *Black* will check that the + reformatted code still produces a valid AST that is effectively equivalent to the + original (see the + `Pragmatism <./the_black_code_style/current_style.html#pragmatism>`_ + section for details). If you're feeling confident, use ``--fast``. + +.. note:: + :doc:`Black is licensed under the MIT license `. Testimonials ------------ +**Mike Bayer**, author of `SQLAlchemy `_: + + *I can't think of any single tool in my entire programming career that has given me a + bigger productivity increase by its introduction. I can now do refactorings in about + 1% of the keystrokes that it would have taken me previously when we had no way for + code to format itself.* + **Dusty Phillips**, `writer `_: *Black is opinionated so you don't have to be.* @@ -42,27 +64,68 @@ and `pipenv `_: *This vastly improves the formatting of our code. Thanks a ton!* + +Show your style +--------------- + +Use the badge in your project's README.md: + +.. code-block:: md + + [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black) + + +Using the badge in README.rst: + +.. code-block:: rst + + .. image:: https://img.shields.io/badge/code%20style-black-000000.svg + :target: https://github.com/psf/black + +Looks like this: + +.. image:: https://img.shields.io/badge/code%20style-black-000000.svg + :target: https://github.com/psf/black + Contents -------- +.. toctree:: + :maxdepth: 3 + :includehidden: + + the_black_code_style/index + +.. toctree:: + :maxdepth: 3 + :includehidden: + :caption: User Guide + + getting_started + usage_and_configuration/index + integrations/index + guides/index + faq + .. toctree:: :maxdepth: 2 + :includehidden: + :caption: Development - installation_and_usage - the_black_code_style - pyproject_toml - editor_integration - version_control_integration - ignoring_unmodified_files - contributing - show_your_style + contributing/index change_log - reference/reference_summary authors +.. toctree:: + :hidden: + :caption: Project Links + + GitHub + PyPI + Chat + Indices and tables ================== * :ref:`genindex` -* :ref:`modindex` * :ref:`search`