<span style=" font-size:10pt;font-family:sans-serif"><i>> I think we
should stay with the traditional 80 characters per line.</i></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Seconded. </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><rant></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">When I was younger
I thought this was a silly requirement, a remnant from the age of serial
terminals....</span>
<br><span style=" font-size:10pt;font-family:sans-serif">So I allowed myself
to relax these checks - and indeed, the tools allow developers to do so.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">But with experience,
I realised the side effects - and in reverse, the positive impact this
limit has on the code and its maintainability...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">It forces people
to avoid writing lengthy one-liners that only they themselves comprehend....
(<i>and given the power of Python's expressiveness, this can become quite
an issue, real fast</i>)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">It e.g. forces
the introduction of "interim" variables, holding interim results
of a big computation... instead of huge expressions with insane nesting
levels.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"></rant></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">My vote is on
PEP8 as-is - that is, 80 columns..</span>
<br>
<br><span style=" font-size:10pt;color:#000080;font-family:sans-serif"><b>Thanassis
Tsiodras</b></span>
<br><span style=" font-size:10pt;font-family:sans-serif">Real-time Embedded
Software Engineer </span>
<br><span style=" font-size:10pt;font-family:sans-serif">System, Software
and Technology Department</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><b>ESTEC</b></span>
<br><span style=" font-size:10pt;font-family:sans-serif">Keplerlaan 1,
PO Box 299</span>
<br><span style=" font-size:10pt;font-family:sans-serif">NL-2200 AG Noordwijk,
The Netherlands</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Thanassis.Tsiodras@esa.int
| </span><a href=www.esa.int><span style=" font-size:10pt;color:blue;font-family:sans-serif">www.esa.int</span></a>
<br><span style=" font-size:10pt;font-family:sans-serif">T +31 71 565 5332</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Sebastian
Huber" <sebastian.huber@embedded-brains.de></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Christian
Mauderer" <christian.mauderer@embedded-brains.de>, "Chris
Johns" <chrisj@rtems.org>, "Christian Mauderer" <list@c-mauderer.de>,
devel@rtems.org</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">19/03/2020
07:24</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
RFC: Exceptions to PEP-8 Adoption for RTEMS Tools</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"devel"
<devel-bounces@rtems.org></span>
<br>
<hr noshade>
<br>
<br>
<br><span style=" font-size:12pt">On 19/03/2020 07:07, Christian Mauderer
wrote:</span>
<br><tt><span style=" font-size:12pt">I think we will have a really hard
time to set up tools like formatters<br>
or pylint to check and use these rules. I think setting a line length to<br>
120 should be easy to possible for nearly any tool. But I expect that<br>
setting it to 120 for code and 80 for comments can be _very_ difficult<br>
depending on the tool.<br>
<br>
<br>
PS: Reason for me being not a fan of long lines: While programming I<br>
often use a split window. In that configuration my editor can show 112<br>
columns in each window on my current screen. That fits well for nearly<br>
all code that follows the 80 character convention. But for example your<br>
proposed length of 120 the code will lead to either a smaller font, a<br>
lot of random line breaks done by the editor or to loosing one window.<br>
Again: It's not a strong opinion and I'll accept 120 too. But expect<br>
that some others have stronger opinions about 80 characters.<br>
</span></tt>
<br><tt><span style=" font-size:12pt">I run everything in text mode under
tmux and in Emacs I split vertically and<br>
variable length is painful and prefer we settle on 80.<br>
</span></tt>
<br><tt><span style=" font-size:12pt">Maybe let's wait whether there are
more opinions. Currently we have<br>
<br>
- one clear vote for 120 lines (Amar)<br>
- one clear vote for 80 lines (Chris)<br>
- one a bit undecided with tendency to shorter lines (myself)</span></tt>
<br><span style=" font-size:12pt">I think we should stay with the traditional
80 characters per line. It is also recommended by the Google Python Style
Guide:</span>
<br><a href="http://google.github.io/styleguide/pyguide.html#32-line-length"><span style=" font-size:12pt;color:blue"><u>http://google.github.io/styleguide/pyguide.html#32-line-length</u></span></a>
<br><span style=" font-size:12pt">It allows some exceptions which all make
sense from my point of view.</span>
<br><tt><span style=" font-size:10pt">_______________________________________________<br>
devel mailing list<br>
devel@rtems.org<br>
</span></tt><a href=http://lists.rtems.org/mailman/listinfo/devel><tt><span style=" font-size:10pt">http://lists.rtems.org/mailman/listinfo/devel</span></tt></a>
<br>
<br><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>