[Python-ideas] Linking Doug's stdlib documentation to our main modules doc.

Ian Bicking ianb at colorstudy.com
Sun Mar 20 00:58:50 CET 2011

On Sat, Mar 19, 2011 at 5:47 PM, Raymond Hettinger <
raymond.hettinger at gmail.com> wrote:

> On Mar 19, 2011, at 3:29 PM, Nick Coghlan wrote:
> >
> > Good: just link them all as part of the module documentation
> > generation process. Some people may understand the stdlib docs better,
> > some may understand PyMOTW better, but providing ready access to both
> > is unlikely to actively *confuse* anyone that wasn't already lost.
> It is interesting how this thread continues to press ahead
> even after Doug himself has said "it seems best to treat
> PyMOTW as a separately maintained resource and let users
> find it separately".
> The seems unequivocal to me.

Doug's in the awkward position that we're all kind of talking about him ;)
If I was in his place I know I'd feel weird about it and kind of want to
avoid the discussion; which would be fine, and it's fine if Doug feels like
avoiding this discussion.  If he's really bothered by it, or feels that
inclusion of links would be a problem, okay, but I read his statement as
meaning he didn't feel confident championing, or maybe even advocating, the
inclusion of links himself.  But people aren't advocating for those links on
Doug's behalf either, the advocacy is for a perceived benefit to document

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20110319/5cedc539/attachment.html>

More information about the Python-ideas mailing list