Author gvanrossum
Recipients Friedrich.Spee.von.Langenfeld, SilentGhost, belopolsky, docs@python, ezio.melotti, gvanrossum, r.david.murray, rhettinger, terry.reedy
Date 2016-01-06.05:11:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452057118.69.0.667059089543.issue22558@psf.upfronthosting.co.za>
In-reply-to
Content
It's fine to add a source link to any module for which there is Python source code.  I suppose this adds a slight maintenance burden when a module moves (e.g. when a module is turned into a package, or when the subdirectory structure of the Lib directory changes).

I'm a little confused about the "New in x.y" note -- why is that connected to the source code link?

Of course, the source tells a different story from the docs -- e.g. undocumented implementation details may change, and sometimes the source is hard to understand (on occasion I've been confused myself :-).  But Python is open source, so people can always read the source -- I don't see why we should try to make reading the source harder for people who don't yet have the chops to just read it on their own computer!
History
Date User Action Args
2016-01-06 05:11:58gvanrossumsetrecipients: + gvanrossum, rhettinger, terry.reedy, belopolsky, ezio.melotti, r.david.murray, SilentGhost, docs@python, Friedrich.Spee.von.Langenfeld
2016-01-06 05:11:58gvanrossumsetmessageid: <1452057118.69.0.667059089543.issue22558@psf.upfronthosting.co.za>
2016-01-06 05:11:58gvanrossumlinkissue22558 messages
2016-01-06 05:11:58gvanrossumcreate