Black: An uncompromising Python code formatter

Re:Black: An uncompromising Python code formatter by klodolph on Friday May 25, 2018 @03:55PM (#17157310)

When I read that line in the documentation, it hurt a little. I'm going to be honest here. I did not feel good with someone saying that an 80-column limit is just there to pad my paycheck, rather than an informed decision I made. I realize that it was tongue in cheek, but it still felt bad.

[ Parent | on HN ]

Re:Black: An uncompromising Python code formatter by sametmax on Friday May 25, 2018 @04:39PM (#17157745)

If that hurt you, you need bigger problems in life.

[ Parent | on HN ]

Re:Black: An uncompromising Python code formatter by ubernostrum on Friday May 25, 2018 @06:45PM (#17158751)

I like a line length rule because I use an editor that can show me multiple files side-by-side, and keeping things to a certain length ensures that I can productively do that.

And my terminal happens to be around 240 characters wide for the font size I use and the size of my laptop's screen, which means if I limit to 80 characters or less I can snugly fit three files, or if I set to 100 I can get two with some breathing room.

Plus, if a line really is going over those lengths, then it's often a code smell: maybe I've got code that's too complex and ending up deeply-nested, or maybe I've got functions or methods taking way too many arguments, and hitting a line-length rule will warn me about that.

[ Parent | on HN ]

Re:Black: An uncompromising Python code formatter by klodolph on Friday May 25, 2018 @05:06PM (#17157986)

Why are you being so dismissive? It seems like you are making this into some kind of contest to see who has bigger problems.

I am just being honest, and I think I am being helpful because other people will also react negatively to the way the documentation is written. I support the project and want it to be successful, providing feedback like this achieves progress towards that goal, in my estimation.

[ Parent | on HN ]