X-Git-Url: https://git.madduck.net/etc/vim.git/blobdiff_plain/7c556faf5fc0747e60d85ff2a77e8138f9fd8b6b..47861a6a3b847026bfc677ae896fbcbe171347ae:/README.md?ds=sidebyside
diff --git a/README.md b/README.md
index dc93b37..7aa988a 100644
--- a/README.md
+++ b/README.md
@@ -1,14 +1,14 @@
-![Black Logo](https://raw.githubusercontent.com/python/black/master/docs/_static/logo2-readme.png)
+![Black Logo](https://raw.githubusercontent.com/psf/black/master/docs/_static/logo2-readme.png)
The Uncompromising Code Formatter
-
+
-
-
+
+
-
+
> âAny color you like.â
@@ -178,14 +178,14 @@ great.
```py3
# in:
-l = [1,
+j = [1,
2,
3,
]
# out:
-l = [1, 2, 3]
+j = [1, 2, 3]
```
If not, *Black* will look at the contents of the first outer matching
@@ -373,7 +373,7 @@ The main reason to standardize on a single form of quotes is aesthetics.
Having one kind of quotes everywhere reduces reader distraction.
It will also enable a future version of *Black* to merge consecutive
string literals that ended up on the same line (see
-[#26](https://github.com/python/black/issues/26) for details).
+[#26](https://github.com/psf/black/issues/26) for details).
Why settle on double quotes? They anticipate apostrophes in English
text. They match the docstring standard described in [PEP 257](https://www.python.org/dev/peps/pep-0257/#what-is-a-docstring).
@@ -730,16 +730,16 @@ Configuration:
To install with [vim-plug](https://github.com/junegunn/vim-plug):
```
-Plug 'python/black'
+Plug 'psf/black'
```
or with [Vundle](https://github.com/VundleVim/Vundle.vim):
```
-Plugin 'python/black'
+Plugin 'psf/black'
```
-or you can copy the plugin from [plugin/black.vim](https://github.com/python/black/tree/master/plugin/black.vim).
+or you can copy the plugin from [plugin/black.vim](https://github.com/psf/black/tree/master/plugin/black.vim).
Let me know if this requires any changes to work with Vim 8's builtin
`packadd`, or Pathogen, and so on.
@@ -900,7 +900,7 @@ installed](https://pre-commit.com/#install), add this to the
`.pre-commit-config.yaml` in your repository:
```yaml
repos:
-- repo: https://github.com/python/black
+- repo: https://github.com/psf/black
rev: stable
hooks:
- id: black
@@ -974,16 +974,16 @@ and [`pipenv`](https://docs.pipenv.org/):
Use the badge in your project's README.md:
```markdown
-[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/python/black)
+[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
```
Using the badge in README.rst:
```
.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
- :target: https://github.com/python/black
+ :target: https://github.com/psf/black
```
-Looks like this: [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/python/black)
+Looks like this: [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
## License
@@ -1045,6 +1045,12 @@ More details can be found in [CONTRIBUTING](CONTRIBUTING.md).
* if *Black* puts parenthesis around a single expression, it moves comments
to the wrapped expression instead of after the brackets (#872)
+* *Black* is now able to format Python code that uses assignment expressions
+ (`:=` as described in PEP-572) (#935)
+
+* *Black* is now able to format Python code that uses positional-only
+ arguments (`/` as described in PEP-570) (#946)
+
### 19.3b0