Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #65777 > unrolled thread
| Started by | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| First post | 2014-02-09 15:46 -0500 |
| Last post | 2014-02-09 15:46 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: imperative mood in docstrings Terry Reedy <tjreedy@udel.edu> - 2014-02-09 15:46 -0500
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2014-02-09 15:46 -0500 |
| Subject | Re: imperative mood in docstrings |
| Message-ID | <mailman.6599.1391978797.18130.python-list@python.org> |
On 2/9/2014 7:05 AM, bagrat lazaryan wrote:
> pep 257 -- docstring conventions, as well as a myriad of books and other resources, recommend documenting a function's or method's effect as a command ("do this", "return that"), not as a description ("does this", "returns that"). what's the logic behind this recommendation?
The imperative is directed at the Python interpreter. It says what a
call instructs the interpreter to do.
--
Terry Jan Reedy
Back to top | Article view | comp.lang.python
csiph-web