[Python-ideas] Linking Doug's stdlib documentation to our main modules doc.
jnoller at gmail.com
Sat Mar 19 18:27:06 CET 2011
On Fri, Mar 18, 2011 at 6:29 PM, Guido van Rossum <guido at python.org> wrote:
> On Fri, Mar 18, 2011 at 1:48 PM, Ian Bicking <ianb at colorstudy.com> wrote:
>> On Thu, Mar 17, 2011 at 8:47 PM, Steven D'Aprano <steve at pearwood.info>
>>> With all respect to Doug, do we really want to bless his website more than
>>> any of the other Python blogs, tutorials, etc. out on the Internet?
>> Bah humbug. If we could link stdlib docs to every good quality piece of
>> coverage for that module then that would be great. It's not like someone
>> else has been denied, or that we're giving Doug exclusive linking rights or
>> something. It just happens he has written the most comprehensive and
>> maintained set of docs, and so it would be bureaucratically rather easy to
>> get a bunch more helpful links in the docs that will help people learn
>> Python better. Frankly it doesn't matter if it's "blessed" as that doesn't
>> incur any real benefit.
> Good call!
Dougs docs are indispensable. The number of times I have had people at
work and elsewhere come to me and ask "why aren't the PMOTW in, or
linked to from the stdlib docs" is astounding. People consider them
*better* resources than the stdlib docs right now. We shouldn't be
afraid to link to real, valuable resources that enhance peoples'
ability to learn the language and the standard library.
I don't agree with the hand waving around broken links, the fact the
Doug wrote a book, endorsements, etc. The fact is, he's written better
docs on many things, and we're doing the community a disservice by not
actively exposing them as supplements to the existing documentation.
Why is it so hard to simply do the right thing here?
More information about the Python-ideas