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/128857.html below:

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

[Python-Dev] Best practice for documentation for std lib [Python-Dev] Best practice for documentation for std libEthan Furman ethan at stoneleaf.us
Sun Sep 22 18:32:31 CEST 2013
On 09/22/2013 08:49 AM, Barry Warsaw wrote:
> On Sep 22, 2013, at 10:34 AM, Brett Cannon wrote:
>
>> The rule of thumb I go by is the docstring should be enough to answer the
>> question "what args does this thing take and what does it do in general to
>> know it's the function I want and another one in the same module?" quickly
>> and succinctly; i.e. just enough so that help() reminds you about details
>> for a module you are already familiar with that might come up while at the
>> interpreter prompt. Everything else -- in-depth discussion of the
>> algorithms, extra examples, why you want to use this function, etc. -- all
>> go in the .rst docs.
>
> That's exactly my own rule of thumb too, so +1.

Another +1.  So it that three rules or three thumbs?  ;)

--
~Ethan~
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