]> git.madduck.net Git - etc/vim.git/commit

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 / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 136930f) | patch
Don't let TokenError bubble up from lib2to3_parse (GH-2343)
authorTanvi Moharir <74228962+tanvimoharir@users.noreply.github.com>
Sat, 4 Dec 2021 20:21:26 +0000 (01:51 +0530)
committerGitHub <noreply@github.com>
Sat, 4 Dec 2021 20:21:26 +0000 (15:21 -0500)
commitf52cb0fe3775829245acfeae191e8d63120c8416
tree724bd60c952530e9128b3b8a0c320182f8e03543tree | snapshot
parent136930fccb99320865622e12ffc21bdd45fd7501commit | diff
Don't let TokenError bubble up from lib2to3_parse (GH-2343)

error: cannot format <string>: ('EOF in multi-line statement', (2, 0))

 ▲ before ▼ after

error: cannot format <string>: Cannot parse: 2:0: EOF in multi-line statement

Co-authored-by: Richard Si <63936253+ichard26@users.noreply.github.com>
CHANGES.md diff | blob | history
src/black/parsing.py diff | blob | history
tests/test_black.py diff | blob | history
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.