for -- else: what was the motivation?

[Peter J. Holzer]

On 2022-10-10 10:11:10 +0000, Stefan Ram wrote:
>   I would not use tabs in source code as they are not
>   displayed in the same way everywhere.

Some would argue that this is a feature. Different people prefer
different indentation widths. Using a single tab character for an
indentation level allows everybody to view the file in their preferred
layout.

I have, however, found out that this requires more discipline than I and
the people I work with can muster. There is always someone who
accidentally converts some tabs to spaces, messing up indentation for
everyone else. So I require a "indent by x spaces" rule for all projects
I work on (unless the language convention have a strong preference for
tabs, like in Go).

In email I would always use spaces. Tabs are just too unreliable there.


>   Functions also come at a cost. From the Web:
                                   ^^^^^^^^^^^^
Ah yes. Your infamous aversion against useful citations strikes again.

For those too lazy to use a search engine, the excerpt seems to be from
https://softwarebyscience.com/very-short-functions-are-a-code-smell-an-overview-of-the-science-on-function-length/

        hp

-- 
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp at hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://mail.python.org/pipermail/python-list/attachments/20221013/2f76f202/attachment.sig>