From: Stephen F. <st...@th...> - 2024-04-17 16:14:50
|
On Wed, 2024-04-17 at 09:03 -0500, Karl O. Pinc wrote: > On Wed, 17 Apr 2024 11:02:11 +0100 > Stephen Finucane <st...@th...ru> wrote: > > > On Tue, 2024-04-16 at 19:45 +0000, Guenter Milde via Docutils-develop > > wrote: > > > > "black" seems too rigid to me (practicability beats purity), > > > especially as we have a large codebase with long legacy and must > > > rely on "git blame" in many cases to find out whether some legacy > > > code may be dropped or has a reason... > > > > I too have some concerns with the style of black-formatted code - as > > I do with the style of gofmt-formatted Go code - however, it _is_ > > robustly maintained, requires little to no configuration on our end, > > and effectively allows formatting to be ignored by developers. > > Unsolicited input. It seems now would be the time to comment, > even though I am unlikely to ever be involved. > > I like (the traditional) 79 char line length limit. > black --line-length 79 ... > isort --line-length 79 ... > > (Black defaults to 88.) > > There's a reason newspapers are written in columns. > The eye must track back from the end of one line > to the beginning of the next. This is disturbed by > over-long lines. I agree. > > Regards, > > Karl <ko...@ka...> > Free Software: "You don't pay back, you pay forward." > -- Robert A. Heinlein |