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 chris.jerdonek
Recipients brett.cannon, chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan
Date 2012-11-19.02:33:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353292397.55.0.590134272911.issue16506@psf.upfronthosting.co.za>
In-reply-to
Content
> The link does nothing because what is directly below the TOC link is the table of contents.

Yes, that's the impression one gets when the link doesn't work.  But the links below are just the sections for the current page rather than the table of contents for the devguide.  Compare, for example, the left column here:

http://docs.python.org/dev/library/argparse.html

The table of contents for the devguide can go on a separate page like it's done for the Python documentation.  We can decide what level of sectioning to display (assuming Sphinx lets you configure that).  Personally, I think I would prefer a shallow TOC (i.e. one or two levels).
History
Date User Action Args
2012-11-19 02:33:17chris.jerdoneksetrecipients: + chris.jerdonek, brett.cannon, ncoghlan, ezio.melotti, eric.araujo
2012-11-19 02:33:17chris.jerdoneksetmessageid: <1353292397.55.0.590134272911.issue16506@psf.upfronthosting.co.za>
2012-11-19 02:33:17chris.jerdoneklinkissue16506 messages
2012-11-19 02:33:16chris.jerdonekcreate