This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, docs@python, eric.araujo, pitrou, r.david.murray, rhettinger
Date 2011-01-07.21:52:00
SpamBayes Score 2.2185587e-12
Marked as misclassified No
Message-id <AANLkTinjsCjNkuGENAe3YXJ-mjyc-g3mCeVUxTAZcCxy@mail.gmail.com>
In-reply-to <1294435943.46.0.999211081532.issue10858@psf.upfronthosting.co.za>
Content
On Fri, Jan 7, 2011 at 4:32 PM, Éric Araujo <report@bugs.python.org> wrote:
..
> 3: Not all modules are good examples (see threading for some unelegant code), so I support ad-hoc selection.

The problem with ad-hoc selection is that it adds maintenance burden
(someone has to make a call) and it is inherently subjective.  For
example, I find dis.py source code rather uninspiring while
pickletools.py has a trove of valuable information about pickle
opcodes that is not available elsewhere.

>  I also support the real fix of improving the quality of every module, but that’s longer-term. :)

Having the sources on "public display" may help achieving this goal.

> 4: “Show Source” is a link that is easily overlooked IMO, a seealso section makes me think people
> will actually see the link.

A side-bar link may be in addition to the more prominent but less
common "See also" links.  If the source navigation becomes available,
we can also add inconspicuous links to function sectoins that would
take you directly to the function source code.
History
Date User Action Args
2011-01-07 21:52:01belopolskysetrecipients: + belopolsky, rhettinger, pitrou, eric.araujo, r.david.murray, docs@python
2011-01-07 21:52:00belopolskylinkissue10858 messages
2011-01-07 21:52:00belopolskycreate