actions/black
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Create indentation FAQ entry (#2855)

Browse Source 
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
This commit is contained in:
Felix Hildén 2022-02-02 08:59:42 +02:00 committed by GitHub
parent 111880efc7
commit 31fe97e7ce
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/faq.md
View File

@ -8,6 +8,18 @@ The most common questions and issues users face are aggregated to this FAQ.
:class: this-will-duplicate-information-and-it-is-still-useful-here :class: this-will-duplicate-information-and-it-is-still-useful-here
``` ```
## Why spaces? I prefer tabs
PEP 8 recommends spaces over tabs, and they are used by most of the Python community.
_Black_ provides no options to configure the indentation style, and requests for such
options will not be considered.
However, we recognise that using tabs is an accessibility issue as well. While the
option will never be added to _Black_, visually impaired developers may find conversion
tools such as `expand/unexpand` (for Linux) useful when contributing to Python projects.
A workflow might consist of e.g. setting up appropriate pre-commit and post-merge git
hooks, and scripting `unexpand` to run after applying _Black_.
## Does Black have an API? ## Does Black have an API?
Not yet. _Black_ is fundamentally a command line tool. Many Not yet. _Black_ is fundamentally a command line tool. Many