Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #73948
| References | <53B59358.2040404@tobiah.org> |
|---|---|
| Date | 2014-07-04 12:44 +0200 |
| Subject | Re: PEP8 and 4 spaces |
| From | Chris “Kwpolska” Warrick <kwpolska@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.11487.1404470682.18130.python-list@python.org> (permalink) |
On Thu, Jul 3, 2014 at 7:31 PM, Tobiah <tshepard@rcsreg.com> wrote: > Anyway, I gave up the 80 char line length long > ago, having little feeling for some dolt on > a Weiss terminal that for some reason needs to > edit my code. And yet, you did not give up an even more insane line length limit, in e-mail. The longest line in your original message is a measly 57 characters long. The median line length is 46 characters. Which is pretty insane, and ultra-hard to read. You can do more in e-mail. > Each line of characters MUST be no more than 998 characters, and > SHOULD be no more than 78 characters, excluding the CRLF. That's the standard, [RFC 5322][]; the exact same quote appeared back in [RFC 2822][]. However, many places actually want you to use a bit less; common values include 70 or 72. But still, it is MUCH more roomy and readable than the value you use. Here are the line lengths in the original message: [47, 45, 45, 46, 46, 47, 45, 5, 46, 43, 46, 47, 47, 49, 31, 57, 52, 34, 42, 23] [RFC 5322]: http://tools.ietf.org/html/rfc5322#section-2.1.1 [RFC 2822]: http://tools.ietf.org/html/rfc2822#section-2.1.1 -- Chris “Kwpolska” Warrick <http://kwpolska.tk> PGP: 5EAAEA16 stop html mail | always bottom-post | only UTF-8 makes sense
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: PEP8 and 4 spaces Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-07-04 12:44 +0200
csiph-web