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, pitrou, r.david.murray, rhettinger
Date 2011-01-07.21:17:58
SpamBayes Score 1.2621676e-10
Marked as misclassified No
Message-id <1294435080.29.0.970097612809.issue10858@psf.upfronthosting.co.za>
In-reply-to
Content
As Raymond explained, he added these links as a kind of social experiment and this issue itself shows that it works. :-)

I have a few suggestions on how to make these links more useful:

1. A ViewVC link is the simplest solution to present the source, but the way it presents the source code looks foreign to sphinx docs.  It would be better if the source was formatted similarly to the source examples embedded in doc pages.

2. It would be great to have at least module names hyperlinked in the source views to aid code navigation.

3. I would rather see source links appear consistently for each module and not just for an ad-hoc selection.

4. The side bar already has a "Show Source" link which takes to the reST source of the page.  I don't think this is very useful.  Maybe this link should point to the Python source or a separate "python source" link should appear next to it.
History
Date User Action Args
2011-01-07 21:18:00belopolskysetrecipients: + belopolsky, rhettinger, pitrou, r.david.murray, docs@python
2011-01-07 21:18:00belopolskysetmessageid: <1294435080.29.0.970097612809.issue10858@psf.upfronthosting.co.za>
2011-01-07 21:17:58belopolskylinkissue10858 messages
2011-01-07 21:17:58belopolskycreate