News for hackers. Stuff that matters.
Re:Black, the uncompromising Python code formatter, is stable by tayo42 on Saturday January 29, 2022 @07:54PM (#30132433)
> If it doesn't show up in the syntax tree, it doesn't have meaning.

Why did you use paragraphs to write your comment then? People read the code thats written.

Re:Black, the uncompromising Python code formatter, is stable by solarmist on Saturday January 29, 2022 @09:23PM (#30133218)
Auto formatters support paragraphs, but they don't support I'm going to give this paragraph 2 blank lines because it's particularly important/complicated/blah.
Re:Black, the uncompromising Python code formatter, is stable by mumblemumble on Saturday January 29, 2022 @11:14PM (#30133954)
Typographic standards typically don't, either. Fortunately, there's more than one way to convey emphasis.

Also, single functions that are long enough to contain something analogous to paragraphs are arguably not Pythonic in the first place.

Re:Black, the uncompromising Python code formatter, is stable by solarmist on Saturday January 29, 2022 @11:22PM (#30134003)
For paragraph I just mean a series of 1 or more lines separated by a blank line vs no blank lines.
Re:Black, the uncompromising Python code formatter, is stable by Mawr on Sunday January 30, 2022 @03:49AM (#30135143)
Are there two blank lines between these parts of the code for a reason or did the person who wrote this code make a mistake?

If that part of the code is special for whatever reason, add a comment saying why.

Re:Black, the uncompromising Python code formatter, is stable by tayo42 on Saturday January 29, 2022 @09:48PM (#30133375)
Oh interesting thanks! I couldn't find it in the docs before
Re:Black, the uncompromising Python code formatter, is stable by solarmist on Saturday January 29, 2022 @10:54PM (#30133823)
Yeah, I don't think it's mentioned because it feels like supporting spaces between words, I’d guess. Just so fundamental a functionality it's assumed.
Re:Black, the uncompromising Python code formatter, is stable by Qub3d on Sunday January 30, 2022 @02:15AM (#30134795)
I think the argument is not that structure should be dispensed, or that it doesn't matter, rather that a given style convention is fungible, and we should probably all just pick something good enough and get on with it, because the code will execute regardless of whether we use " or ' around our strings.

Spend some time considering the language standards, but then ship it for god's sake.

See also from Peter Norvig[0]:

* Get involved in a language standardization effort. It could be the ANSI C++ committee, or it could be deciding if your local coding style will have 2 or 4 space indentation levels. Either way, you learn about what other people like in a language, how deeply they feel so, and perhaps even a little about why they feel so.

* Have the good sense to get off the language standardization effort as quickly as possible.

[0]:https://www.norvig.com/21-days.html

Re:Black, the uncompromising Python code formatter, is stable by tayo42 on Sunday January 30, 2022 @11:12AM (#30138399)
I actually had this formatter thing happen at work. We have code that generates more python code. Now the quotes are changed and we need escapes because a rule it being applied. Escapes are harder to read and look messier.