John Litborn

Discussions that's happened in Black, for context: #2316 - main issue discussing different ways of handling long type hints https://github.com/psf/black/pull/3930 - PR that handled long type hints in a different...

> @jakkdl thanks for linking the issues and giving me some more context. > > > PR that handled long type hints in a different way, abandoned after seeing the...

> I started putting together a PR to prepare an alpha for the 2024 stable style, and here's a few thoughts: > > > * The test suite found a...

> Replying to a few recent posts (including my own): > > @Fatal1ty > > > I like this idea with Ellipsis on the same line (there is no longer...

Heya, author of #3899 here. The behaviour makes sense to me, since the type could also be long. ```python class A: attr1: my_long_very_custom_type_bla_bla_bla = "111111111111111111111111111111111111111111111111111111" ``` makes sense to me...

Ooh that's nice! I guess I could switch to a workflow where I write everything in a long line and let black handle line splits, but I would like it...

It's also not too rare that I write a multiline string, format it for consistent line length, but then reword / drop a word from an early sentence, and then...

Right, so a temp workaround (with preview) is to just join two of the lines and then let Black go at it. Hell yeah, Black or Bust 🤘

preview still won't reformat the original example, which I think is going to be quite common in existing code due to this not having been enforced previously, so I don't...

I've started looking at this - sharing some WIP thoughts: ### compared to variable annotations variable annotations have to include parentheses (because you cannot write inline annotations, e.g. `(x: int,...