RFC: Exceptions to PEP-8 Adoption for RTEMS Tools

[Sebastian Huber]

On 19/03/2020 07:07, Christian Mauderer wrote:

>>> I think we will have a really hard time to set up tools like formatters
>>> or pylint to check and use these rules. I think setting a line length to
>>> 120 should be easy to possible for nearly any tool. But I expect that
>>> setting it to 120 for code and 80 for comments can be_very_  difficult
>>> depending on the tool.
>>>
>>>
>>> PS: Reason for me being not a fan of long lines: While programming I
>>> often use a split window. In that configuration my editor can show 112
>>> columns in each window on my current screen. That fits well for nearly
>>> all code that follows the 80 character convention. But for example your
>>> proposed length of 120 the code will lead to either a smaller font, a
>>> lot of random line breaks done by the editor or to loosing one window.
>>> Again: It's not a strong opinion and I'll accept 120 too. But expect
>>> that some others have stronger opinions about 80 characters.
>> I run everything in text mode under tmux and in Emacs I split vertically and
>> variable length is painful and prefer we settle on 80.
> Maybe let's wait whether there are more opinions. Currently we have
>
> - one clear vote for 120 lines (Amar)
> - one clear vote for 80 lines (Chris)
> - one a bit undecided with tendency to shorter lines (myself)

I think we should stay with the traditional 80 characters per line. It 
is also recommended by the Google Python Style Guide:

http://google.github.io/styleguide/pyguide.html#32-line-length

It allows some exceptions which all make sense from my point of view.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200319/10bd6157/attachment-0001.html>