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 eric.araujo
Recipients brett.cannon, docs@python, eric.araujo, ezio.melotti, fdrake, georg.brandl, rhettinger, sandro.tosi
Date 2011-08-19.13:33:02
SpamBayes Score 2.7225706e-05
Marked as misclassified No
Message-id <1313760783.84.0.770084926143.issue12409@psf.upfronthosting.co.za>
In-reply-to
Content
From IRC:

<fdrake> After last being pressed on this, I got to thinking about it more.  Back in the day, that's all the doc there was about the tool-chain.  With Sphinx standing as a successful independent project, the tool documentation need no longer be part of any of the python.org docs; what's left probably can be moved.
<fdrake> (Yes, I'm withdrawing my objection.)

So, I am in favor of moving the Python-specific parts of Doc/documenting (if any) to the devguide and just link to the upstream Sphinx docs (which are a subset of our Doc/documenting) for the markup and suchlike.
History
Date User Action Args
2011-08-19 13:33:03eric.araujosetrecipients: + eric.araujo, fdrake, brett.cannon, georg.brandl, rhettinger, ezio.melotti, sandro.tosi, docs@python
2011-08-19 13:33:03eric.araujosetmessageid: <1313760783.84.0.770084926143.issue12409@psf.upfronthosting.co.za>
2011-08-19 13:33:03eric.araujolinkissue12409 messages
2011-08-19 13:33:02eric.araujocreate