A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-September/128915.html below:

[Python-Dev] Best practice for documentation for std lib

[Python-Dev] Best practice for documentation for std libTerry Reedy tjreedy at udel.edu
Mon Sep 23 19:52:28 CEST 2013
On 9/23/2013 10:56 AM, Guido van Rossum wrote:

> I think 60 is just a guideline. In stdlib .py source code I want it not
> to extend beyond the 79th column (see recent PEP 8 argument). For a

PEP 8 says "Limit all lines to a maximum of 79 characters.

For flowing long blocks of text with fewer structural restrictions 
(docstrings or comments), the line length should be limited to 72 
characters."

I do not understand 72 instead of 79, but to me, that means 72 chars 
total, including indents, triple quote and period, which means the 
cursor not past 73. If that is not what you mean, please clarify.

> typical class, where the docstring is indented 4 spaces, that leaves 72
> characters for the summary line (including a final period!). For a
> method it's 68 due to the extra indent.

72 - 2 indents - """ - . = 60, which is a bit skimpy ;-). Why not the 
full 79 at least?

-- 
Terry Jan Reedy

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4