Package: black Version: 21.12b0-1 Severity: normal X-Debbugs-Cc: s...@debian.org, Neil Williams <codeh...@debian.org>, Sylvestre Ledru <sylves...@debian.org>, Chris Lamb <la...@debian.org>
The Black project has made it's first stable release, and it even has a defined stability policy! https://black.readthedocs.io/en/stable/the_black_code_style/index.html#stability-policy I'm happy to read that a potentially large risk of disruptive change will now only occur be once a year :-D Changelog is available here: https://github.com/psf/black/blob/main/CHANGES.md Reverse Depends: elpa-elpy python3-typer python3-schema-salad python3-pylsp-black python3-cogent3 python3-pyls-black lava-dev I would prefer if someone else would update and upload, because I'm not sure to what degree the changes affect the rdeps, and I don't want to carelessly make trouble for others. Also, I'm not sure if the documented issues related to mypyc affect our Black package, nor if these issues represent a regression between 21.12b0 and 22.1.0. My stake in this is Elpy, which is finally actively maintained again. At this time, the upstream snapshot of Elpy (merged to salsa) FTBFS due to missing/bad/changed pyproject.toml parsing support in Black, and obviously it's a better use of time and goodwill to target the stable version (which we want in Debian) rather than the current version. I concede that the bug may be in Elpy, and in this case it makes sense to fix it for a year rather than fix it for backwards compat with a beta release of Black. Kind regards, Nicholas
