{
"info": {
"author": "Bastian Venthur",
"author_email": "mail@venthur.de",
"bugtrack_url": null,
"classifiers": [
"Development Status :: 4 - Beta",
"Environment :: Console",
"Intended Audience :: Developers",
"License :: OSI Approved :: MIT License",
"Operating System :: OS Independent",
"Programming Language :: Python",
"Programming Language :: Python :: 3.6",
"Programming Language :: Python :: 3.7",
"Programming Language :: Python :: 3 :: Only",
"Topic :: Software Development :: Libraries :: Python Modules",
"Topic :: Software Development :: Quality Assurance"
],
"description": "# Why Noir?\n\nNoir is a drop-in replacement for Black with a default line length set to 79\ncharacters.\n\nTo replace black you only need to replace `black` with `noir` in the\nrequirements.txt and/or setup.py.\n\nNoir provides the binary `black` so you don't have to change anything else in\nyour build pipeline.\n\n\n\n
The Uncompromising Code Formatter
\n\n
\n\n\n\n\n\n\n\n
\n\n> \u201cAny color you like.\u201d\n\n\n*Black* is the uncompromising Python code formatter. By using it, you\nagree to cede control over minutiae of hand-formatting. In return,\n*Black* gives you speed, determinism, and freedom from `pycodestyle`\nnagging about formatting. You will save time and mental energy for\nmore important matters.\n\nBlackened code looks the same regardless of the project you're reading.\nFormatting becomes transparent after a while and you can focus on the\ncontent instead.\n\n*Black* makes code review faster by producing the smallest diffs\npossible.\n\nTry it out now using the [Black Playground](https://black.now.sh).\nWatch the [PyCon 2019 talk](https://youtu.be/esZLCuWs_2Y) to learn more.\n\n---\n\n*Contents:* **[Installation and usage](#installation-and-usage)** |\n**[Code style](#the-black-code-style)** |\n**[pyproject.toml](#pyprojecttoml)** |\n**[Editor integration](#editor-integration)** |\n**[blackd](#blackd)** |\n**[Version control integration](#version-control-integration)** |\n**[Ignoring unmodified files](#ignoring-unmodified-files)** |\n**[Used by](#used-by)** |\n**[Testimonials](#testimonials)** |\n**[Show your style](#show-your-style)** |\n**[Contributing](#contributing-to-black)** |\n**[Change Log](#change-log)** |\n**[Authors](#authors)**\n\n---\n\n## Installation and usage\n\n### Installation\n\n*Black* can be installed by running `pip install noir`. It requires\nPython 3.6.0+ to run but you can reformat Python 2 code with it, too.\n\n\n### Usage\n\nTo get started right away with sensible defaults:\n\n```\nblack {source_file_or_directory}\n```\n\n### Command line options\n\n*Black* doesn't provide many options. You can list them by running\n`black --help`:\n\n```text\nblack [OPTIONS] [SRC]...\n\nOptions:\n -c, --code TEXT Format the code passed in as a string.\n -l, --line-length INTEGER How many characters per line to allow.\n [default: 79]\n -t, --target-version [py27|py33|py34|py35|py36|py37|py38]\n Python versions that should be supported by\n Black's output. [default: per-file auto-\n detection]\n --py36 Allow using Python 3.6-only syntax on all\n input files. This will put trailing commas\n in function signatures and calls also after\n *args and **kwargs. Deprecated; use\n --target-version instead. [default: per-file\n auto-detection]\n --pyi Format all input files like typing stubs\n regardless of file extension (useful when\n piping source on standard input).\n -S, --skip-string-normalization\n Don't normalize string quotes or prefixes.\n --check Don't write the files back, just return the\n status. Return code 0 means nothing would\n change. Return code 1 means some files\n would be reformatted. Return code 123 means\n there was an internal error.\n --diff Don't write the files back, just output a\n diff for each file on stdout.\n --fast / --safe If --fast given, skip temporary sanity\n checks. [default: --safe]\n --include TEXT A regular expression that matches files and\n directories that should be included on\n recursive searches. An empty value means\n all files are included regardless of the\n name. Use forward slashes for directories\n on all platforms (Windows, too). Exclusions\n are calculated first, inclusions later.\n [default: \\.pyi?$]\n --exclude TEXT A regular expression that matches files and\n directories that should be excluded on\n recursive searches. An empty value means no\n paths are excluded. Use forward slashes for\n directories on all platforms (Windows, too).\n Exclusions are calculated first, inclusions\n later. [default: /(\\.eggs|\\.git|\\.hg|\\.mypy\n _cache|\\.nox|\\.tox|\\.venv|_build|buck-\n out|build|dist)/]\n -q, --quiet Don't emit non-error messages to stderr.\n Errors are still emitted, silence those with\n 2>/dev/null.\n -v, --verbose Also emit messages to stderr about files\n that were not changed or were ignored due to\n --exclude=.\n --version Show the version and exit.\n --config PATH Read configuration from PATH.\n -h, --help Show this message and exit.\n```\n\n*Black* is a well-behaved Unix-style command-line tool:\n* it does nothing if no sources are passed to it;\n* it will read from standard input and write to standard output if `-`\n is used as the filename;\n* it only outputs messages to users on standard error;\n* exits with code 0 unless an internal error occurred (or `--check` was\n used).\n\n\n### NOTE: This is a beta product\n\n*Black* is already [successfully used](#used-by) by many projects, small and big.\nIt also sports a decent test suite. However, it is still very new.\nThings will probably be wonky for a while. This is made explicit by the\n\"Beta\" trove classifier, as well as by the \"b\" in the version number.\nWhat this means for you is that **until the formatter becomes stable,\nyou should expect some formatting to change in the future**. That being\nsaid, no drastic stylistic changes are planned, mostly responses to bug\nreports.\n\nAlso, as a temporary safety measure, *Black* will check that the\nreformatted code still produces a valid AST that is equivalent to the\noriginal. This slows it down. If you're feeling confident, use\n``--fast``.\n\n\n## The *Black* code style\n\n*Black* reformats entire files in place. It is not configurable. It\ndoesn't take previous formatting into account. It doesn't reformat\nblocks that start with `# fmt: off` and end with `# fmt: on`. `# fmt: on/off`\nhave to be on the same level of indentation. It also\nrecognizes [YAPF](https://github.com/google/yapf)'s block comments to\nthe same effect, as a courtesy for straddling code.\n\n\n### How *Black* wraps lines\n\n*Black* ignores previous formatting and applies uniform horizontal\nand vertical whitespace to your code. The rules for horizontal\nwhitespace can be summarized as: do whatever makes `pycodestyle` happy.\nThe coding style used by *Black* can be viewed as a strict subset of\nPEP 8.\n\nAs for vertical whitespace, *Black* tries to render one full expression\nor simple statement per line. If this fits the allotted line length,\ngreat.\n```py3\n# in:\n\nl = [1,\n 2,\n 3,\n]\n\n# out:\n\nl = [1, 2, 3]\n```\n\nIf not, *Black* will look at the contents of the first outer matching\nbrackets and put that in a separate indented line.\n```py3\n# in:\n\nImportantClass.important_method(exc, limit, lookup_lines, capture_locals, extra_argument)\n\n# out:\n\nImportantClass.important_method(\n exc, limit, lookup_lines, capture_locals, extra_argument\n)\n```\n\nIf that still doesn't fit the bill, it will decompose the internal\nexpression further using the same rule, indenting matching brackets\nevery time. If the contents of the matching brackets pair are\ncomma-separated (like an argument list, or a dict literal, and so on)\nthen *Black* will first try to keep them on the same line with the\nmatching brackets. If that doesn't work, it will put all of them in\nseparate lines.\n```py3\n# in:\n\ndef very_important_function(template: str, *variables, file: os.PathLike, engine: str, header: bool = True, debug: bool = False):\n \"\"\"Applies `variables` to the `template` and writes to `file`.\"\"\"\n with open(file, 'w') as f:\n ...\n\n# out:\n\ndef very_important_function(\n template: str,\n *variables,\n file: os.PathLike,\n engine: str,\n header: bool = True,\n debug: bool = False,\n):\n \"\"\"Applies `variables` to the `template` and writes to `file`.\"\"\"\n with open(file, \"w\") as f:\n ...\n```\n\nYou might have noticed that closing brackets are always dedented and\nthat a trailing comma is always added. Such formatting produces smaller\ndiffs; when you add or remove an element, it's always just one line.\nAlso, having the closing bracket dedented provides a clear delimiter\nbetween two distinct sections of the code that otherwise share the same\nindentation level (like the arguments list and the docstring in the\nexample above).\n\nIf a data structure literal (tuple, list, set, dict) or a line of \"from\"\nimports cannot fit in the allotted length, it's always split into one\nelement per line. This minimizes diffs as well as enables readers of\ncode to find which commit introduced a particular entry. This also\nmakes *Black* compatible with [isort](https://pypi.org/p/isort/) with\nthe following configuration.\n\n\nA compatible `.isort.cfg`\n\n```\n[settings]\nmulti_line_output=3\ninclude_trailing_comma=True\nforce_grid_wrap=0\nuse_parentheses=True\nline_length=79\n```\n\nThe equivalent command line is:\n```\n$ isort --multi-line=3 --trailing-comma --force-grid-wrap=0 --use-parentheses --line-width=79 [ file.py ]\n```\n\n\n\n### Empty lines\n\n*Black* avoids spurious vertical whitespace. This is in the spirit of\nPEP 8 which says that in-function vertical whitespace should only be\nused sparingly.\n\n*Black* will allow single empty lines inside functions, and single and\ndouble empty lines on module level left by the original editors, except\nwhen they're within parenthesized expressions. Since such expressions\nare always reformatted to fit minimal space, this whitespace is lost.\n\nIt will also insert proper spacing before and after function definitions.\nIt's one line before and after inner functions and two lines before and\nafter module-level functions and classes. *Black* will not put empty\nlines between function/class definitions and standalone comments that\nimmediately precede the given function/class.\n\n*Black* will enforce single empty lines between a class-level docstring\nand the first following field or method. This conforms to\n[PEP 257](https://www.python.org/dev/peps/pep-0257/#multi-line-docstrings).\n\n*Black* won't insert empty lines after function docstrings unless that\nempty line is required due to an inner function starting immediately\nafter.\n\n\n### Trailing commas\n\n*Black* will add trailing commas to expressions that are split\nby comma where each element is on its own line. This includes function\nsignatures.\n\nUnnecessary trailing commas are removed if an expression fits in one\nline. This makes it 1% more likely that your line won't exceed the\nallotted line length limit. Moreover, in this scenario, if you added\nanother argument to your call, you'd probably fit it in the same line\nanyway. That doesn't make diffs any larger.\n\nOne exception to removing trailing commas is tuple expressions with\njust one element. In this case *Black* won't touch the single trailing\ncomma as this would unexpectedly change the underlying data type. Note\nthat this is also the case when commas are used while indexing. This is\na tuple in disguise: ```numpy_array[3, ]```.\n\nOne exception to adding trailing commas is function signatures\ncontaining `*`, `*args`, or `**kwargs`. In this case a trailing comma\nis only safe to use on Python 3.6. *Black* will detect if your file is\nalready 3.6+ only and use trailing commas in this situation. If you\nwonder how it knows, it looks for f-strings and existing use of trailing\ncommas in function signatures that have stars in them. In other words,\nif you'd like a trailing comma in this situation and *Black* didn't\nrecognize it was safe to do so, put it there manually and *Black* will\nkeep it.\n\n\n### Strings\n\n*Black* prefers double quotes (`\"` and `\"\"\"`) over single quotes (`'`\nand `'''`). It will replace the latter with the former as long as it\ndoes not result in more backslash escapes than before.\n\n*Black* also standardizes string prefixes, making them always lowercase.\nOn top of that, if your code is already Python 3.6+ only or it's using\nthe `unicode_literals` future import, *Black* will remove `u` from the\nstring prefix as it is meaningless in those scenarios.\n\nThe main reason to standardize on a single form of quotes is aesthetics.\nHaving one kind of quotes everywhere reduces reader distraction.\nIt will also enable a future version of *Black* to merge consecutive\nstring literals that ended up on the same line (see\n[#26](https://github.com/psf/black/issues/26) for details).\n\nWhy settle on double quotes? They anticipate apostrophes in English\ntext. They match the docstring standard described in [PEP 257](https://www.python.org/dev/peps/pep-0257/#what-is-a-docstring).\nAn empty string in double quotes (`\"\"`) is impossible to confuse with\na one double-quote regardless of fonts and syntax highlighting used.\nOn top of this, double quotes for strings are consistent with C which\nPython interacts a lot with.\n\nOn certain keyboard layouts like US English, typing single quotes is\na bit easier than double quotes. The latter requires use of the Shift\nkey. My recommendation here is to keep using whatever is faster to type\nand let *Black* handle the transformation.\n\nIf you are adopting *Black* in a large project with pre-existing string\nconventions (like the popular [\"single quotes for data, double quotes for\nhuman-readable strings\"](https://stackoverflow.com/a/56190)), you can\npass `--skip-string-normalization` on the command line. This is meant as\nan adoption helper, avoid using this for new projects.\n\n### Numeric literals\n\n*Black* standardizes most numeric literals to use lowercase letters for the\nsyntactic parts and uppercase letters for the digits themselves: `0xAB`\ninstead of `0XAB` and `1e10` instead of `1E10`. Python 2 long literals are\nstyled as `2L` instead of `2l` to avoid confusion between `l` and `1`.\n\n\n### Line breaks & binary operators\n\n*Black* will break a line before a binary operator when splitting a block\nof code over multiple lines. This is so that *Black* is compliant with the\nrecent changes in the [PEP 8](https://www.python.org/dev/peps/pep-0008/#should-a-line-break-before-or-after-a-binary-operator)\nstyle guide, which emphasizes that this approach improves readability.\n\nThis behaviour may raise ``W503 line break before binary operator`` warnings in\nstyle guide enforcement tools like Flake8. Since ``W503`` is not PEP 8 compliant,\nyou should tell Flake8 to ignore these warnings.\n\n\n### Slices\n\nPEP 8 [recommends](https://www.python.org/dev/peps/pep-0008/#whitespace-in-expressions-and-statements)\nto treat ``:`` in slices as a binary operator with the lowest priority, and to\nleave an equal amount of space on either side, except if a parameter is omitted\n(e.g. ``ham[1 + 1 :]``). It also states that for extended slices, both ``:``\noperators have to have the same amount of spacing, except if a parameter is\nomitted (``ham[1 + 1 ::]``). *Black* enforces these rules consistently.\n\nThis behaviour may raise ``E203 whitespace before ':'`` warnings in style guide\nenforcement tools like Flake8. Since ``E203`` is not PEP 8 compliant, you should\ntell Flake8 to ignore these warnings.\n\n\n### Parentheses\n\nSome parentheses are optional in the Python grammar. Any expression can\nbe wrapped in a pair of parentheses to form an atom. There are a few\ninteresting cases:\n\n- `if (...):`\n- `while (...):`\n- `for (...) in (...):`\n- `assert (...), (...)`\n- `from X import (...)`\n- assignments like:\n - `target = (...)`\n - `target: type = (...)`\n - `some, *un, packing = (...)`\n - `augmented += (...)`\n\nIn those cases, parentheses are removed when the entire statement fits\nin one line, or if the inner expression doesn't have any delimiters to\nfurther split on. If there is only a single delimiter and the expression\nstarts or ends with a bracket, the parenthesis can also be successfully\nomitted since the existing bracket pair will organize the expression\nneatly anyway. Otherwise, the parentheses are added.\n\nPlease note that *Black* does not add or remove any additional nested\nparentheses that you might want to have for clarity or further\ncode organization. For example those parentheses are not going to be\nremoved:\n```py3\nreturn not (this or that)\ndecision = (maybe.this() and values > 0) or (maybe.that() and values < 0)\n```\n\n\n### Call chains\n\nSome popular APIs, like ORMs, use call chaining. This API style is known\nas a [fluent interface](https://en.wikipedia.org/wiki/Fluent_interface).\n*Black* formats those by treating dots that follow a call or an indexing\noperation like a very low priority delimiter. It's easier to show the\nbehavior than to explain it. Look at the example:\n```py3\ndef example(session):\n result = (\n session.query(models.Customer.id)\n .filter(\n models.Customer.account_id == account_id,\n models.Customer.email == email_address,\n )\n .order_by(models.Customer.id.asc())\n .all()\n )\n```\n\n\n### Typing stub files\n\nPEP 484 describes the syntax for type hints in Python. One of the\nuse cases for typing is providing type annotations for modules which\ncannot contain them directly (they might be written in C, or they might\nbe third-party, or their implementation may be overly dynamic, and so on).\n\nTo solve this, [stub files with the `.pyi` file\nextension](https://www.python.org/dev/peps/pep-0484/#stub-files) can be\nused to describe typing information for an external module. Those stub\nfiles omit the implementation of classes and functions they\ndescribe, instead they only contain the structure of the file (listing\nglobals, functions, and classes with their members). The recommended\ncode style for those files is more terse than PEP 8:\n\n* prefer `...` on the same line as the class/function signature;\n* avoid vertical whitespace between consecutive module-level functions,\n names, or methods and fields within a single class;\n* use a single blank line between top-level class definitions, or none\n if the classes are very small.\n\n*Black* enforces the above rules. There are additional guidelines for\nformatting `.pyi` file that are not enforced yet but might be in\na future version of the formatter:\n\n* all function bodies should be empty (contain `...` instead of the body);\n* do not use docstrings;\n* prefer `...` over `pass`;\n* for arguments with a default, use `...` instead of the actual default;\n* avoid using string literals in type annotations, stub files support\n forward references natively (like Python 3.7 code with `from __future__\n import annotations`);\n* use variable annotations instead of type comments, even for stubs that\n target older versions of Python;\n* for arguments that default to `None`, use `Optional[]` explicitly;\n* use `float` instead of `Union[int, float]`.\n\n\n## pyproject.toml\n\n*Black* is able to read project-specific default values for its\ncommand line options from a `pyproject.toml` file. This is\nespecially useful for specifying custom `--include` and `--exclude`\npatterns for your project.\n\n**Pro-tip**: If you're asking yourself \"Do I need to configure anything?\"\nthe answer is \"No\". *Black* is all about sensible defaults.\n\n\n### What on Earth is a `pyproject.toml` file?\n\n[PEP 518](https://www.python.org/dev/peps/pep-0518/) defines\n`pyproject.toml` as a configuration file to store build system\nrequirements for Python projects. With the help of tools\nlike [Poetry](https://poetry.eustace.io/) or\n[Flit](https://flit.readthedocs.io/en/latest/) it can fully replace the\nneed for `setup.py` and `setup.cfg` files.\n\n\n### Where *Black* looks for the file\n\nBy default *Black* looks for `pyproject.toml` starting from the common\nbase directory of all files and directories passed on the command line.\nIf it's not there, it looks in parent directories. It stops looking\nwhen it finds the file, or a `.git` directory, or a `.hg` directory,\nor the root of the file system, whichever comes first.\n\nIf you're formatting standard input, *Black* will look for configuration\nstarting from the current working directory.\n\nYou can also explicitly specify the path to a particular file that you\nwant with `--config`. In this situation *Black* will not look for any\nother file.\n\nIf you're running with `--verbose`, you will see a blue message if\na file was found and used.\n\nPlease note `blackd` will not use `pyproject.toml` configuration.\n\n\n### Configuration format\n\nAs the file extension suggests, `pyproject.toml` is a [TOML](https://github.com/toml-lang/toml) file. It contains separate\nsections for different tools. *Black* is using the `[tool.black]`\nsection. The option keys are the same as long names of options on\nthe command line.\n\nNote that you have to use single-quoted strings in TOML for regular\nexpressions. It's the equivalent of r-strings in Python. Multiline\nstrings are treated as verbose regular expressions by Black. Use `[ ]`\nto denote a significant space character.\n\n\nExample `pyproject.toml`\n\n```toml\n[tool.black]\nline-length = 79\ntarget-version = ['py37']\ninclude = '\\.pyi?$'\nexclude = '''\n\n(\n /(\n \\.eggs # exclude a few common directories in the\n | \\.git # root of the project\n | \\.hg\n | \\.mypy_cache\n | \\.tox\n | \\.venv\n | _build\n | buck-out\n | build\n | dist\n )/\n | foo.py # also separately exclude a file named foo.py in\n # the root of the project\n)\n'''\n```\n\n\n\n### Lookup hierarchy\n\nCommand-line options have defaults that you can see in `--help`.\nA `pyproject.toml` can override those defaults. Finally, options\nprovided by the user on the command line override both.\n\n*Black* will only ever use one `pyproject.toml` file during an entire\nrun. It doesn't look for multiple files, and doesn't compose\nconfiguration from different levels of the file hierarchy.\n\n\n## Editor integration\n\n### Emacs\n\nUse [proofit404/blacken](https://github.com/proofit404/blacken) or\n[Elpy](https://github.com/jorgenschaefer/elpy).\n\n\n### PyCharm/IntelliJ IDEA\n\n1. Install `black`.\n\n```console\n$ pip install noir\n```\n\n2. Locate your `black` installation folder.\n\n On macOS / Linux / BSD:\n\n```console\n$ which black\n/usr/local/bin/black # possible location\n```\n\n On Windows:\n\n```console\n$ where black\n%LocalAppData%\\Programs\\Python\\Python36-32\\Scripts\\black.exe # possible location\n```\n\n3. Open External tools in PyCharm/IntelliJ IDEA\n\n On macOS:\n\n```PyCharm -> Preferences -> Tools -> External Tools```\n\n On Windows / Linux / BSD:\n\n```File -> Settings -> Tools -> External Tools```\n\n4. Click the + icon to add a new external tool with the following values:\n - Name: Black\n - Description: Black is the uncompromising Python code formatter.\n - Program: \n - Arguments: `\"$FilePath$\"`\n\n5. Format the currently opened file by selecting `Tools -> External Tools -> black`.\n - Alternatively, you can set a keyboard shortcut by navigating to `Preferences or Settings -> Keymap -> External Tools -> External Tools - Black`.\n\n6. Optionally, run *Black* on every file save:\n\n 1. Make sure you have the [File Watcher](https://plugins.jetbrains.com/plugin/7177-file-watchers) plugin installed.\n 2. Go to `Preferences or Settings -> Tools -> File Watchers` and click `+` to add a new watcher:\n - Name: Black\n - File type: Python\n - Scope: Project Files\n - Program: \n - Arguments: `$FilePath$`\n - Output paths to refresh: `$FilePath$`\n - Working directory: `$ProjectFileDir$`\n\t- Uncheck \"Auto-save edited files to trigger the watcher\"\n\n\n\n### Wing IDE \n\nWing supports black via the OS Commands tool, as explained in the Wing documentation on [pep8 formatting](https://wingware.com/doc/edit/pep8). The detailed procedure is:\n\n1. Install `black`.\n\n```console\n$ pip install noir\n```\n\n2. Make sure it runs from the command line, e.g.\n\n```console\n$ black --help\n```\n\n3. In Wing IDE, activate the **OS Commands** panel and define the command **black** to execute black on the currently selected file:\n\n- Use the Tools -> OS Commands menu selection\n- click on **+** in **OS Commands** -> New: Command line..\n - Title: black\n - Command Line: black %s\n - I/O Encoding: Use Default \n - Key Binding: F1\n - [x] Raise OS Commands when executed\n - [x] Auto-save files before execution\n - [x] Line mode\n\n4. Select a file in the editor and press **F1** , or whatever key binding you selected in step 3, to reformat the file.\n\n### Vim\n\nCommands and shortcuts:\n\n* `:Black` to format the entire file (ranges not supported);\n* `:BlackUpgrade` to upgrade *Black* inside the virtualenv;\n* `:BlackVersion` to get the current version of *Black* inside the\n virtualenv.\n\nConfiguration:\n* `g:black_fast` (defaults to `0`)\n* `g:black_linelength` (defaults to `88`)\n* `g:black_skip_string_normalization` (defaults to `0`)\n* `g:black_virtualenv` (defaults to `~/.vim/black`)\n\nTo install with [vim-plug](https://github.com/junegunn/vim-plug):\n\n```\nPlug 'psf/black'\n```\n\nor with [Vundle](https://github.com/VundleVim/Vundle.vim):\n\n```\nPlugin 'psf/black'\n```\n\nor you can copy the plugin from [plugin/black.vim](https://github.com/psf/black/tree/master/plugin/black.vim).\nLet me know if this requires any changes to work with Vim 8's builtin\n`packadd`, or Pathogen, and so on.\n\nThis plugin **requires Vim 7.0+ built with Python 3.6+ support**. It\nneeds Python 3.6 to be able to run *Black* inside the Vim process which\nis much faster than calling an external command.\n\nOn first run, the plugin creates its own virtualenv using the right\nPython version and automatically installs *Black*. You can upgrade it later\nby calling `:BlackUpgrade` and restarting Vim.\n\nIf you need to do anything special to make your virtualenv work and\ninstall *Black* (for example you want to run a version from master),\ncreate a virtualenv manually and point `g:black_virtualenv` to it.\nThe plugin will use it.\n\nTo run *Black* on save, add the following line to `.vimrc` or `init.vim`:\n\n```\nautocmd BufWritePre *.py execute ':Black'\n```\n\n**How to get Vim with Python 3.6?**\nOn Ubuntu 17.10 Vim comes with Python 3.6 by default.\nOn macOS with Homebrew run: `brew install vim --with-python3`.\nWhen building Vim from source, use:\n`./configure --enable-python3interp=yes`. There's many guides online how\nto do this.\n\n\n### Visual Studio Code\n\nUse the [Python extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python)\n([instructions](https://code.visualstudio.com/docs/python/editing#_formatting)).\n\n\n### SublimeText 3\n\nUse [sublack plugin](https://github.com/jgirardet/sublack).\n\n\n### Jupyter Notebook Magic\n\nUse [blackcellmagic](https://github.com/csurfer/blackcellmagic).\n\n\n### Python Language Server\n\nIf your editor supports the [Language Server Protocol](https://langserver.org/)\n(Atom, Sublime Text, Visual Studio Code and many more), you can use\nthe [Python Language Server](https://github.com/palantir/python-language-server) with the\n[pyls-black](https://github.com/rupert/pyls-black) plugin.\n\n\n### Atom/Nuclide\n\nUse [python-black](https://atom.io/packages/python-black).\n\n\n### Other editors\n\nOther editors will require external contributions.\n\nPatches welcome! \u2728 \ud83c\udf70 \u2728\n\nAny tool that can pipe code through *Black* using its stdio mode (just\n[use `-` as the file name](https://www.tldp.org/LDP/abs/html/special-chars.html#DASHREF2)).\nThe formatted code will be returned on stdout (unless `--check` was\npassed). *Black* will still emit messages on stderr but that shouldn't\naffect your use case.\n\nThis can be used for example with PyCharm's or IntelliJ's [File Watchers](https://www.jetbrains.com/help/pycharm/file-watchers.html).\n\n## blackd\n\n`blackd` is a small HTTP server that exposes *Black*'s functionality over\na simple protocol. The main benefit of using it is to avoid paying the\ncost of starting up a new *Black* process every time you want to blacken\na file.\n\n### Usage\n\n`blackd` is not packaged alongside *Black* by default because it has additional\ndependencies. You will need to do `pip install noir[d]` to install it.\n\nYou can start the server on the default port, binding only to the local interface\nby running `blackd`. You will see a single line mentioning the server's version,\nand the host and port it's listening on. `blackd` will then print an access log\nsimilar to most web servers on standard output, merged with any exception traces\ncaused by invalid formatting requests.\n\n`blackd` provides even less options than *Black*. You can see them by running\n`blackd --help`:\n\n```text\nUsage: blackd [OPTIONS]\n\nOptions:\n --bind-host TEXT Address to bind the server to.\n --bind-port INTEGER Port to listen on\n --version Show the version and exit.\n -h, --help Show this message and exit.\n```\n\nThere is no official blackd client tool (yet!). You can test that blackd is\nworking using `curl`:\n\n```\nblackd --bind-port 9090 & # or let blackd choose a port\ncurl -s -XPOST \"localhost:9090\" -d \"print('valid')\"\n```\n\n### Protocol\n\n`blackd` only accepts `POST` requests at the `/` path. The body of the request\nshould contain the python source code to be formatted, encoded\naccording to the `charset` field in the `Content-Type` request header. If no\n`charset` is specified, `blackd` assumes `UTF-8`.\n\nThere are a few HTTP headers that control how the source is formatted. These\ncorrespond to command line flags for *Black*. There is one exception to this:\n`X-Protocol-Version` which if present, should have the value `1`, otherwise the\nrequest is rejected with `HTTP 501` (Not Implemented).\n\nThe headers controlling how code is formatted are:\n\n - `X-Line-Length`: corresponds to the `--line-length` command line flag.\n - `X-Skip-String-Normalization`: corresponds to the `--skip-string-normalization`\n command line flag. If present and its value is not the empty string, no string\n normalization will be performed.\n - `X-Fast-Or-Safe`: if set to `fast`, `blackd` will act as *Black* does when\n passed the `--fast` command line flag.\n - `X-Python-Variant`: if set to `pyi`, `blackd` will act as *Black* does when\n passed the `--pyi` command line flag. Otherwise, its value must correspond to\n a Python version or a set of comma-separated Python versions, optionally\n prefixed with `py`. For example, to request code that is compatible\n with Python 3.5 and 3.6, set the header to `py3.5,py3.6`.\n\nIf any of these headers are set to invalid values, `blackd` returns a `HTTP 400`\nerror response, mentioning the name of the problematic header in the message body.\n\nApart from the above, `blackd` can produce the following response codes:\n\n - `HTTP 204`: If the input is already well-formatted. The response body is\n\tempty.\n - `HTTP 200`: If formatting was needed on the input. The response body\n\tcontains the blackened Python code, and the `Content-Type` header is set\n\taccordingly.\n - `HTTP 400`: If the input contains a syntax error. Details of the error are\n\treturned in the response body.\n - `HTTP 500`: If there was any kind of error while trying to format the input.\n\tThe response body contains a textual representation of the error.\n\n## Version control integration\n\nUse [pre-commit](https://pre-commit.com/). Once you [have it\ninstalled](https://pre-commit.com/#install), add this to the\n`.pre-commit-config.yaml` in your repository:\n```yaml\nrepos:\n- repo: https://github.com/psf/black\n rev: stable\n hooks:\n - id: black\n language_version: python3.6\n```\nThen run `pre-commit install` and you're ready to go.\n\nAvoid using `args` in the hook. Instead, store necessary configuration\nin `pyproject.toml` so that editors and command-line usage of Black all\nbehave consistently for your project. See *Black*'s own [pyproject.toml](/pyproject.toml)\nfor an example.\n\nIf you're already using Python 3.7, switch the `language_version`\naccordingly. Finally, `stable` is a tag that is pinned to the latest\nrelease on PyPI. If you'd rather run on master, this is also an option.\n\n\n## Ignoring unmodified files\n\n*Black* remembers files it has already formatted, unless the `--diff` flag is used or\ncode is passed via standard input. This information is stored per-user. The exact\nlocation of the file depends on the *Black* version and the system on which *Black*\nis run. The file is non-portable. The standard location on common operating systems\nis:\n\n* Windows: `C:\\\\Users\\\\AppData\\Local\\black\\black\\Cache\\\\cache...pickle`\n* macOS: `/Users//Library/Caches/black//cache...pickle`\n* Linux: `/home//.cache/black//cache...pickle`\n\n`file-mode` is an int flag that determines whether the file was formatted as 3.6+ only,\nas .pyi, and whether string normalization was omitted.\n\nTo override the location of these files on macOS or Linux, set the environment variable\n`XDG_CACHE_HOME` to your preferred location. For example, if you want to put the cache in\nthe directory you're running *Black* from, set `XDG_CACHE_HOME=.cache`. *Black* will then\nwrite the above files to `.cache/black//`.\n\n## Used by\n\nThe following notable open-source projects trust *Black* with enforcing\na consistent code style: pytest, tox, Pyramid, Django Channels, Hypothesis,\nattrs, SQLAlchemy, Poetry, PyPA applications (Warehouse, Pipenv, virtualenv),\nevery Datadog Agent Integration.\n\nAre we missing anyone? Let us know.\n\n\n## Testimonials\n\n**Dusty Phillips**, [writer](https://smile.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=dusty+phillips):\n\n> *Black* is opinionated so you don't have to be.\n\n**Hynek Schlawack**, [creator of `attrs`](https://www.attrs.org/), core\ndeveloper of Twisted and CPython:\n\n> An auto-formatter that doesn't suck is all I want for Xmas!\n\n**Carl Meyer**, [Django](https://www.djangoproject.com/) core developer:\n\n> At least the name is good.\n\n**Kenneth Reitz**, creator of [`requests`](http://python-requests.org/)\nand [`pipenv`](https://docs.pipenv.org/):\n\n> This vastly improves the formatting of our code. Thanks a ton!\n\n\n## Show your style\n\nUse the badge in your project's README.md:\n\n```markdown\n[](https://github.com/psf/black)\n```\n\nUsing the badge in README.rst:\n```\n.. image:: https://img.shields.io/badge/code%20style-black-000000.svg\n :target: https://github.com/psf/black\n```\n\nLooks like this: [](https://github.com/psf/black)\n\n\n## License\n\nMIT\n\n\n## Contributing to *Black*\n\nIn terms of inspiration, *Black* is about as configurable as *gofmt*.\nThis is deliberate.\n\nBug reports and fixes are always welcome! However, before you suggest a\nnew feature or configuration knob, ask yourself why you want it. If it\nenables better integration with some workflow, fixes an inconsistency,\nspeeds things up, and so on - go for it! On the other hand, if your\nanswer is \"because I don't like a particular formatting\" then you're not\nready to embrace *Black* yet. Such changes are unlikely to get accepted.\nYou can still try but prepare to be disappointed.\n\nMore details can be found in [CONTRIBUTING](CONTRIBUTING.md).\n\n\n## Change Log\n\n### unreleased\n\n* added `black -c` as a way to format code passed from the command line\n (#761)\n\n* --safe now works with Python 2 code (#840)\n\n* fixed grammar selection for Python 2-specific code (#765)\n\n* fixed feature detection for trailing commas in function definitions\n and call sites (#763)\n\n* *Black* can now format async generators (#593)\n\n* *Black* no longer crashes on Windows machines with more than 61 cores\n (#838)\n\n* *Black* no longer crashes on standalone comments prepended with\n a backslash (#767)\n\n* *Black* no longer crashes on `from` ... `import` blocks with comments\n (#829)\n\n* removed unnecessary parentheses around `yield` expressions (#834)\n\n* added parentheses around long tuples in unpacking assignments (#832)\n\n* fixed bug that led *Black* format some code with a line length target\n of 1 (#762)\n\n* *Black* no longer introduces quotes in f-string subexpressions on string\n boundaries (#863)\n\n* if *Black* puts parenthesis around a single expression, it moves comments\n to the wrapped expression instead of after the brackets (#872)\n\n* *Black* is now able to format Python code that uses assignment expressions\n (`:=` as described in PEP-572) (#935)\n\n* *Black* is now able to format Python code that uses positional-only\n arguments (`/` as described in PEP-570) (#946)\n\n\n### 19.3b0\n\n* new option `--target-version` to control which Python versions\n *Black*-formatted code should target (#618)\n\n* deprecated `--py36` (use `--target-version=py36` instead) (#724)\n\n* *Black* no longer normalizes numeric literals to include `_` separators (#696)\n\n* long `del` statements are now split into multiple lines (#698)\n\n* type comments are no longer mangled in function signatures\n\n* improved performance of formatting deeply nested data structures (#509)\n\n* *Black* now properly formats multiple files in parallel on\n Windows (#632)\n\n* *Black* now creates cache files atomically which allows it to be used\n in parallel pipelines (like `xargs -P8`) (#673)\n\n* *Black* now correctly indents comments in files that were previously\n formatted with tabs (#262)\n\n* `blackd` now supports CORS (#622)\n\n\n### 18.9b0\n\n* numeric literals are now formatted by *Black* (#452, #461, #464, #469):\n\n * numeric literals are normalized to include `_` separators on Python 3.6+ code\n\n * added `--skip-numeric-underscore-normalization` to disable the above behavior and\n leave numeric underscores as they were in the input\n\n * code with `_` in numeric literals is recognized as Python 3.6+\n\n * most letters in numeric literals are lowercased (e.g., in `1e10`, `0x01`)\n\n * hexadecimal digits are always uppercased (e.g. `0xBADC0DE`)\n\n* added `blackd`, see [its documentation](#blackd) for more info (#349)\n\n* adjacent string literals are now correctly split into multiple lines (#463)\n\n* trailing comma is now added to single imports that don't fit on a line (#250)\n\n* cache is now populated when `--check` is successful for a file which speeds up\n consecutive checks of properly formatted unmodified files (#448)\n\n* whitespace at the beginning of the file is now removed (#399)\n\n* fixed mangling [pweave](http://mpastell.com/pweave/) and\n [Spyder IDE](https://pythonhosted.org/spyder/) special comments (#532)\n\n* fixed unstable formatting when unpacking big tuples (#267)\n\n* fixed parsing of `__future__` imports with renames (#389)\n\n* fixed scope of `# fmt: off` when directly preceding `yield` and other nodes (#385)\n\n* fixed formatting of lambda expressions with default arguments (#468)\n\n* fixed ``async for`` statements: *Black* no longer breaks them into separate\n lines (#372)\n\n* note: the Vim plugin stopped registering ``,=`` as a default chord as it turned out\n to be a bad idea (#415)\n\n\n### 18.6b4\n\n* hotfix: don't freeze when multiple comments directly precede `# fmt: off` (#371)\n\n\n### 18.6b3\n\n* typing stub files (`.pyi`) now have blank lines added after constants (#340)\n\n* `# fmt: off` and `# fmt: on` are now much more dependable:\n\n * they now work also within bracket pairs (#329)\n\n * they now correctly work across function/class boundaries (#335)\n\n * they now work when an indentation block starts with empty lines or misaligned\n comments (#334)\n\n* made Click not fail on invalid environments; note that Click is right but the\n likelihood we'll need to access non-ASCII file paths when dealing with Python source\n code is low (#277)\n\n* fixed improper formatting of f-strings with quotes inside interpolated\n expressions (#322)\n\n* fixed unnecessary slowdown when long list literals where found in a file\n\n* fixed unnecessary slowdown on AST nodes with very many siblings\n\n* fixed cannibalizing backslashes during string normalization\n\n* fixed a crash due to symbolic links pointing outside of the project directory (#338)\n\n\n### 18.6b2\n\n* added `--config` (#65)\n\n* added `-h` equivalent to `--help` (#316)\n\n* fixed improper unmodified file caching when `-S` was used\n\n* fixed extra space in string unpacking (#305)\n\n* fixed formatting of empty triple quoted strings (#313)\n\n* fixed unnecessary slowdown in comment placement calculation on lines without\n comments\n\n\n### 18.6b1\n\n* hotfix: don't output human-facing information on stdout (#299)\n\n* hotfix: don't output cake emoji on non-zero return code (#300)\n\n\n### 18.6b0\n\n* added `--include` and `--exclude` (#270)\n\n* added `--skip-string-normalization` (#118)\n\n* added `--verbose` (#283)\n\n* the header output in `--diff` now actually conforms to the unified diff spec\n\n* fixed long trivial assignments being wrapped in unnecessary parentheses (#273)\n\n* fixed unnecessary parentheses when a line contained multiline strings (#232)\n\n* fixed stdin handling not working correctly if an old version of Click was\n used (#276)\n\n* *Black* now preserves line endings when formatting a file in place (#258)\n\n\n### 18.5b1\n\n* added `--pyi` (#249)\n\n* added `--py36` (#249)\n\n* Python grammar pickle caches are stored with the formatting caches, making\n *Black* work in environments where site-packages is not user-writable (#192)\n\n* *Black* now enforces a PEP 257 empty line after a class-level docstring\n (and/or fields) and the first method\n\n* fixed invalid code produced when standalone comments were present in a trailer\n that was omitted from line splitting on a large expression (#237)\n\n* fixed optional parentheses being removed within `# fmt: off` sections (#224)\n\n* fixed invalid code produced when stars in very long imports were incorrectly\n wrapped in optional parentheses (#234)\n\n* fixed unstable formatting when inline comments were moved around in\n a trailer that was omitted from line splitting on a large expression\n (#238)\n\n* fixed extra empty line between a class declaration and the first\n method if no class docstring or fields are present (#219)\n\n* fixed extra empty line between a function signature and an inner\n function or inner class (#196)\n\n\n### 18.5b0\n\n* call chains are now formatted according to the\n [fluent interfaces](https://en.wikipedia.org/wiki/Fluent_interface)\n style (#67)\n\n* data structure literals (tuples, lists, dictionaries, and sets) are\n now also always exploded like imports when they don't fit in a single\n line (#152)\n\n* slices are now formatted according to PEP 8 (#178)\n\n* parentheses are now also managed automatically on the right-hand side\n of assignments and return statements (#140)\n\n* math operators now use their respective priorities for delimiting multiline\n expressions (#148)\n\n* optional parentheses are now omitted on expressions that start or end\n with a bracket and only contain a single operator (#177)\n\n* empty parentheses in a class definition are now removed (#145, #180)\n\n* string prefixes are now standardized to lowercase and `u` is removed\n on Python 3.6+ only code and Python 2.7+ code with the `unicode_literals`\n future import (#188, #198, #199)\n\n* typing stub files (`.pyi`) are now formatted in a style that is consistent\n with PEP 484 (#207, #210)\n\n* progress when reformatting many files is now reported incrementally\n\n* fixed trailers (content with brackets) being unnecessarily exploded\n into their own lines after a dedented closing bracket (#119)\n\n* fixed an invalid trailing comma sometimes left in imports (#185)\n\n* fixed non-deterministic formatting when multiple pairs of removable parentheses\n were used (#183)\n\n* fixed multiline strings being unnecessarily wrapped in optional\n parentheses in long assignments (#215)\n\n* fixed not splitting long from-imports with only a single name\n\n* fixed Python 3.6+ file discovery by also looking at function calls with\n unpacking. This fixed non-deterministic formatting if trailing commas\n where used both in function signatures with stars and function calls\n with stars but the former would be reformatted to a single line.\n\n* fixed crash on dealing with optional parentheses (#193)\n\n* fixed \"is\", \"is not\", \"in\", and \"not in\" not considered operators for\n splitting purposes\n\n* fixed crash when dead symlinks where encountered\n\n\n### 18.4a4\n\n* don't populate the cache on `--check` (#175)\n\n\n### 18.4a3\n\n* added a \"cache\"; files already reformatted that haven't changed on disk\n won't be reformatted again (#109)\n\n* `--check` and `--diff` are no longer mutually exclusive (#149)\n\n* generalized star expression handling, including double stars; this\n fixes multiplication making expressions \"unsafe\" for trailing commas (#132)\n\n* *Black* no longer enforces putting empty lines behind control flow statements\n (#90)\n\n* *Black* now splits imports like \"Mode 3 + trailing comma\" of isort (#127)\n\n* fixed comment indentation when a standalone comment closes a block (#16, #32)\n\n* fixed standalone comments receiving extra empty lines if immediately preceding\n a class, def, or decorator (#56, #154)\n\n* fixed `--diff` not showing entire path (#130)\n\n* fixed parsing of complex expressions after star and double stars in\n function calls (#2)\n\n* fixed invalid splitting on comma in lambda arguments (#133)\n\n* fixed missing splits of ternary expressions (#141)\n\n\n### 18.4a2\n\n* fixed parsing of unaligned standalone comments (#99, #112)\n\n* fixed placement of dictionary unpacking inside dictionary literals (#111)\n\n* Vim plugin now works on Windows, too\n\n* fixed unstable formatting when encountering unnecessarily escaped quotes\n in a string (#120)\n\n\n### 18.4a1\n\n* added `--quiet` (#78)\n\n* added automatic parentheses management (#4)\n\n* added [pre-commit](https://pre-commit.com) integration (#103, #104)\n\n* fixed reporting on `--check` with multiple files (#101, #102)\n\n* fixed removing backslash escapes from raw strings (#100, #105)\n\n\n### 18.4a0\n\n* added `--diff` (#87)\n\n* add line breaks before all delimiters, except in cases like commas, to\n better comply with PEP 8 (#73)\n\n* standardize string literals to use double quotes (almost) everywhere\n (#75)\n\n* fixed handling of standalone comments within nested bracketed\n expressions; *Black* will no longer produce super long lines or put all\n standalone comments at the end of the expression (#22)\n\n* fixed 18.3a4 regression: don't crash and burn on empty lines with\n trailing whitespace (#80)\n\n* fixed 18.3a4 regression: `# yapf: disable` usage as trailing comment\n would cause *Black* to not emit the rest of the file (#95)\n\n* when CTRL+C is pressed while formatting many files, *Black* no longer\n freaks out with a flurry of asyncio-related exceptions\n\n* only allow up to two empty lines on module level and only single empty\n lines within functions (#74)\n\n\n### 18.3a4\n\n* `# fmt: off` and `# fmt: on` are implemented (#5)\n\n* automatic detection of deprecated Python 2 forms of print statements\n and exec statements in the formatted file (#49)\n\n* use proper spaces for complex expressions in default values of typed\n function arguments (#60)\n\n* only return exit code 1 when --check is used (#50)\n\n* don't remove single trailing commas from square bracket indexing\n (#59)\n\n* don't omit whitespace if the previous factor leaf wasn't a math\n operator (#55)\n\n* omit extra space in kwarg unpacking if it's the first argument (#46)\n\n* omit extra space in [Sphinx auto-attribute comments](http://www.sphinx-doc.org/en/stable/ext/autodoc.html#directive-autoattribute)\n (#68)\n\n\n### 18.3a3\n\n* don't remove single empty lines outside of bracketed expressions\n (#19)\n\n* added ability to pipe formatting from stdin to stdin (#25)\n\n* restored ability to format code with legacy usage of `async` as\n a name (#20, #42)\n\n* even better handling of numpy-style array indexing (#33, again)\n\n\n### 18.3a2\n\n* changed positioning of binary operators to occur at beginning of lines\n instead of at the end, following [a recent change to PEP 8](https://github.com/python/peps/commit/c59c4376ad233a62ca4b3a6060c81368bd21e85b)\n (#21)\n\n* ignore empty bracket pairs while splitting. This avoids very weirdly\n looking formattings (#34, #35)\n\n* remove a trailing comma if there is a single argument to a call\n\n* if top level functions were separated by a comment, don't put four\n empty lines after the upper function\n\n* fixed unstable formatting of newlines with imports\n\n* fixed unintentional folding of post scriptum standalone comments\n into last statement if it was a simple statement (#18, #28)\n\n* fixed missing space in numpy-style array indexing (#33)\n\n* fixed spurious space after star-based unary expressions (#31)\n\n\n### 18.3a1\n\n* added `--check`\n\n* only put trailing commas in function signatures and calls if it's\n safe to do so. If the file is Python 3.6+ it's always safe, otherwise\n only safe if there are no `*args` or `**kwargs` used in the signature\n or call. (#8)\n\n* fixed invalid spacing of dots in relative imports (#6, #13)\n\n* fixed invalid splitting after comma on unpacked variables in for-loops\n (#23)\n\n* fixed spurious space in parenthesized set expressions (#7)\n\n* fixed spurious space after opening parentheses and in default\n arguments (#14, #17)\n\n* fixed spurious space after unary operators when the operand was\n a complex expression (#15)\n\n\n### 18.3a0\n\n* first published version, Happy \ud83c\udf70 Day 2018!\n\n* alpha quality\n\n* date-versioned (see: https://calver.org/)\n\n\n## Authors\n\nGlued together by [\u0141ukasz Langa](mailto:lukasz@langa.pl).\n\nMaintained with [Carol Willing](mailto:carolcode@willingconsulting.com),\n[Carl Meyer](mailto:carl@oddbird.net),\n[Jelle Zijlstra](mailto:jelle.zijlstra@gmail.com),\n[Mika Naylor](mailto:mail@autophagy.io), and\n[Zsolt Dollenstein](mailto:zsol.zsol@gmail.com).\n\nMultiple contributions by:\n* [Anthony Sottile](mailto:asottile@umich.edu)\n* [Artem Malyshev](mailto:proofit404@gmail.com)\n* [Benjamin Woodruff](mailto:github@benjam.info)\n* [Christian Heimes](mailto:christian@python.org)\n* [Daniel M. Capella](mailto:polycitizen@gmail.com)\n* [Eli Treuherz](mailto:eli@treuherz.com)\n* hauntsaninja\n* Hugo van Kemenade\n* [Ivan Katani\u0107](mailto:ivan.katanic@gmail.com)\n* [Jason Fried](mailto:me@jasonfried.info)\n* [Jonas Obrist](mailto:ojiidotch@gmail.com)\n* [Luka Sterbic](mailto:luka.sterbic@gmail.com)\n* [Miguel Gaiowski](mailto:miggaiowski@gmail.com)\n* [Miroslav Shubernetskiy](mailto:miroslav@miki725.com)\n* [Neraste](mailto:neraste.herr10@gmail.com)\n* [Osaetin Daniel](mailto:osaetindaniel@gmail.com)\n* [Peter Bengtsson](mailto:mail@peterbe.com)\n* [Stavros Korokithakis](mailto:hi@stavros.io)\n* [Sunil Kapil](mailto:snlkapil@gmail.com)\n* [Utsav Shah](mailto:ukshah2@illinois.edu)\n* [Vishwas B Sharma](mailto:sharma.vishwas88@gmail.com)\n* [Chuck Wooters](mailto:chuck.wooters@microsoft.com)\n\n\n",
"description_content_type": "text/markdown",
"docs_url": null,
"download_url": "",
"downloads": {
"last_day": -1,
"last_month": -1,
"last_week": -1
},
"home_page": "https://github.com/venthur/noir",
"keywords": "automation formatter yapf autopep8 pyfmt gofmt rustfmt",
"license": "MIT",
"maintainer": "",
"maintainer_email": "",
"name": "noir",
"package_url": "https://pypi.org/project/noir/",
"platform": "",
"project_url": "https://pypi.org/project/noir/",
"project_urls": {
"Homepage": "https://github.com/venthur/noir"
},
"release_url": "https://pypi.org/project/noir/19.3b0/",
"requires_dist": [
"appdirs",
"attrs (>=18.1.0)",
"click (>=6.5)",
"toml (>=0.9.4)",
"typed-ast (>=1.3.1)",
"aiohttp-cors ; extra == 'd'",
"aiohttp (>=3.3.2) ; extra == 'd'"
],
"requires_python": ">=3.6",
"summary": "The uncompromising code formatter.",
"version": "19.3b0"
},
"last_serial": 5713821,
"releases": {
"19.3b0": [
{
"comment_text": "",
"digests": {
"md5": "b11b81fffd9da8504dc13d03668edadd",
"sha256": "1eb6bef5dbc98fbc4a603644c091e26c1e5fa1a460765d84b7d8c64fd66f8fd6"
},
"downloads": -1,
"filename": "noir-19.3b0-py36-none-any.whl",
"has_sig": false,
"md5_digest": "b11b81fffd9da8504dc13d03668edadd",
"packagetype": "bdist_wheel",
"python_version": "py36",
"requires_python": ">=3.6",
"size": 94476,
"upload_time": "2019-08-22T08:11:21",
"url": "https://files.pythonhosted.org/packages/77/35/5f218366ec35c5e88c612da8d46adf34602547318b4108a4448e04378434/noir-19.3b0-py36-none-any.whl"
},
{
"comment_text": "",
"digests": {
"md5": "575b5d2fee56d84a4efa80792908980d",
"sha256": "e9086aa2e8b03ac6dd95c7d6050e351ca08ed2d774c676e51a23a9e4b00a5757"
},
"downloads": -1,
"filename": "noir-19.3b0.tar.gz",
"has_sig": false,
"md5_digest": "575b5d2fee56d84a4efa80792908980d",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 184851,
"upload_time": "2019-08-22T08:11:25",
"url": "https://files.pythonhosted.org/packages/fe/49/4690a1b71fa2312cc63509332289db2fe67aad5b3bdfa9e727a8bb156e2e/noir-19.3b0.tar.gz"
}
]
},
"urls": [
{
"comment_text": "",
"digests": {
"md5": "b11b81fffd9da8504dc13d03668edadd",
"sha256": "1eb6bef5dbc98fbc4a603644c091e26c1e5fa1a460765d84b7d8c64fd66f8fd6"
},
"downloads": -1,
"filename": "noir-19.3b0-py36-none-any.whl",
"has_sig": false,
"md5_digest": "b11b81fffd9da8504dc13d03668edadd",
"packagetype": "bdist_wheel",
"python_version": "py36",
"requires_python": ">=3.6",
"size": 94476,
"upload_time": "2019-08-22T08:11:21",
"url": "https://files.pythonhosted.org/packages/77/35/5f218366ec35c5e88c612da8d46adf34602547318b4108a4448e04378434/noir-19.3b0-py36-none-any.whl"
},
{
"comment_text": "",
"digests": {
"md5": "575b5d2fee56d84a4efa80792908980d",
"sha256": "e9086aa2e8b03ac6dd95c7d6050e351ca08ed2d774c676e51a23a9e4b00a5757"
},
"downloads": -1,
"filename": "noir-19.3b0.tar.gz",
"has_sig": false,
"md5_digest": "575b5d2fee56d84a4efa80792908980d",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 184851,
"upload_time": "2019-08-22T08:11:25",
"url": "https://files.pythonhosted.org/packages/fe/49/4690a1b71fa2312cc63509332289db2fe67aad5b3bdfa9e727a8bb156e2e/noir-19.3b0.tar.gz"
}
]
}
![\"Build](\"https://travis-ci.com/psf/black.svg?branch=master\")
\n![\"Coverage](\"https://coveralls.io/repos/github/psf/black/badge.svg?branch=master\"){kind=icon}
\n![\"License:](\"https://black.readthedocs.io/en/stable/_static/license.svg\")
\n![\"PyPI\"](\"https://black.readthedocs.io/en/stable/_static/pypi.svg\")
\n![\"Code](\"https://img.shields.io/badge/code%20style-black-000000.svg\"){kind=icon}
\n