Micha Reiser

One open question is whether we want to support multiple formatter edition (or at least one old edition). It took the community a long time to upgrade to Ruff 0.2

> Hey @MichaReiser I'd be interested in picking up #11216. Let me know if this is alright. Thanks! Sure. Feel free to give it a go. I don't know what...

@bnkc how is it going with the docstring bug? Do you need help or did you decide not to work on it (which is fine)? I'm asking because I'm considering...

@dhruvmanila, do you remember what the open decisions were on the f-string formatting and what the remaining work is for it to be stabilized? Do you know if black implemented...

Regarding f-string formatting. We should look into whether it plays nicely with https://github.com/astral-sh/ruff/blob/ae9c6a9255294cb5cc884726fcbfbcd441f2f76c/crates/ruff_python_formatter/src/other/arguments.rs#L221 From looking at the `is_multiline` implementation I get the impression that it is an over-approximation and a...

Black's plan is to stabilize all preview styles, but none of the unstable features which aligns with what I outlined in the summary. https://github.com/psf/black/issues/4501

> Are there any plans to incorporate allowing empty new lines after certain code blocks from #9745 ? No, allowing empty lines after clause header is not planned for the...

> I'm late for this issue, can we have a stable output of [docs.astral.sh/ruff/formatter/black#call-expressions-with-a-single-multiline-string-argument](https://docs.astral.sh/ruff/formatter/black/#call-expressions-with-a-single-multiline-string-argument) ? > > If it's too late for stable 2025 style, is it possible to be...

> Ideally I feel like I'd like the second line of the "spillover" for very long error messages to be indented, rather than the first line. Not sure how tricky...

Hi @fraser-langton > I think it's pretty standard to put after all other imports Could you share some reference suggesting that putting `TYPE_CHECKING` last is the standard? I did a...