]> git.madduck.net Git - etc/vim.git/blobdiff - README.md

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

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.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

projects / etc / vim.git / blobdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | inline | side by side
Update changelog for PR 249.
[etc/vim.git] / README.md
diff --git a/README.md b/README.md
index af1f8479f358e9b55bccc917c3ef0b540a6c02a4..77b077c29b5bfcd3f10db1dec47dcd0276303fb8 100644 (file)
--- a/README.md
+++ b/README.md
@@ -380,7 +380,7 @@ decision = (maybe.this() and values > 0) or (maybe.that() and values < 0)
 
 Some popular APIs, like ORMs, use call chaining.  This API style is known
 as a [fluent interface](https://en.wikipedia.org/wiki/Fluent_interface).
-*Black* formats those treating dots that follow a call or an indexing
+*Black* formats those by treating dots that follow a call or an indexing
 operation like a very low priority delimiter.  It's easier to show the
 behavior than to explain it.  Look at the example:
 ```py3
@@ -653,6 +653,11 @@ More details can be found in [CONTRIBUTING](CONTRIBUTING.md).
 
 ### 18.5b1 (unreleased)
 
+* Added `--pyi` option to force pyi-style formatting (regardless of file
+  extension, or when piping source to *Black*), and `--py36` option to force
+  allowing Py36 syntax (e.g. trailing commas after `*args` or `**kwargs`), even
+  if the file doesn't currently use any 3.6-only syntax (#249)
+
 * Python grammar pickle caches are stored with the formatting caches, making
   *Black* work in environments where site-packages is not user-writable (#192)
 
@@ -666,7 +671,7 @@ More details can be found in [CONTRIBUTING](CONTRIBUTING.md).
 
 * fixed unstable formatting when inline comments were moved around in
   a trailer that was omitted from line splitting on a large expression
-  (#238) 
+  (#238)
 
 ### 18.5b0
 
vim configuration

Legalese

All content available in this repository is copyright © martin f. krafft, unless otherwise noted.

All files and their content are released under the terms of the Artistic Licence 2.0, unless otherwise noted.

The operator of this repository shall not be held liable for offending content in pages linking to or linked from these page, nor does he endorse their content unless stated otherwise.