Guido van Rossum added the comment: [Guido] >>- Regarding line length, I think it is reasonable to mention that many >>- organizations are settling on 100 as a compromise. On newer laptops you >>- can still fit two terminal windows (with a reasonable font size) side by >>- side. (Also many people checking code into the stdlib ignore the 80 char >>- limit. :-( )
[Barry] > Really? I haven't seen much 100 character limits. Have you seen this at > Google or Dropbox? At Google people argue to raise the 80 char limit forever -- and they use 2-space indents. For Java they've accepted 100 chars. At Dropbox they also use 100 chars (although nobody enforces style rules here, so many lines are even longer :-( ). > (The only argument against such things is of course the pep8 tool, which > codifies the recommendations in this PEP. Some packages actually run the pep8 > checker as part of their test suite, so if we change a recommendation and that > gets pulled into pep8, then tests can break.) I hate that tool. It only covers a small part of the PEP, and is very nitpicky about the part it does support, causing people to contort their code to shut up the tool instead of learning and understanding the PEP and applying common sense. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18472> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
