Path to this page:
Subject: CVS commit: pkgsrc/textproc/py-black
From: Adam Ciarcinski
Date: 2023-04-17 21:27:28
Message id: 20230417192728.B10DDFA85@cvs.NetBSD.org
Log Message:
py-black: updated to 23.3.0
23.3.0
Highlights
This release fixes a longstanding confusing behavior in Black's GitHub action, \
where the
version of the action did not determine the version of Black being run. In
addition, there is a small bug fix around imports and a number of improvements to the
preview style.
Please try out the
[preview \
style](https://black.readthedocs.io/en/stable/the_black_code_style/future_style.html#preview-style)
with `black --preview` and tell us your feedback. All changes in the preview \
style are
expected to become part of Black's stable style in January 2024.
Stable style
- Import lines with `# fmt: skip` and `# fmt: off` no longer have an extra blank line
added when they are right after another import line
Preview style
- Add trailing commas to collection literals even if there's a comment after the last
entry
- `async def`, `async for`, and `async with` statements are now formatted \
consistently
compared to their non-async version.
- `with` statements that contain two context managers will be consistently wrapped in
parentheses
- Let string splitters respect [East Asian \
Width](https://www.unicode.org/reports/tr11/)
- Now long string literals can be split after East Asian commas and periods \
(`、` U+3001
IDEOGRAPHIC COMMA, `。` U+3002 IDEOGRAPHIC FULL STOP, & `,` U+FF0C \
FULLWIDTH COMMA)
besides before spaces
- For stubs, enforce one blank line after a nested class with a body other than just
`...`
- Improve handling of multiline strings by changing line split behavior
Parser
- Added support for formatting files with invalid type comments
Integrations
- Update GitHub Action to use the version of Black equivalent to action's version if
version input is not specified
- Fix missing Python binary path in autoload script for vim
Documentation
- Document that only the most recent release is supported for security issues;
vulnerabilities should be reported through Tidelift
Files: