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-22.23:38:19
SpamBayes Score 0.0026789072
Marked as misclassified No
Message-id <1314056300.6.0.0554640165983.issue12409@psf.upfronthosting.co.za>
In-reply-to
Content
My comment was ambiguous, let me rephrase it: I am in favor of moving cpython/Doc/documenting to the devguide.  Then, in the devguide, I would like to remove all the doc that’s just duplicating the upstream Sphinx docs, keeping only links and Python-specific parts.

> But one aspect I think it needs to be done as a prerequisite to this migration is:
> standardizing the sphinx/tools versions used to build the doc.
If this gets rejected, we can move the Documenting tree to the devguide anyway, we’ll just have to add a few paragraphs for 2.7 differences.
History
Date User Action Args
2011-08-22 23:38:20eric.araujosetrecipients: + eric.araujo, fdrake, brett.cannon, georg.brandl, rhettinger, ezio.melotti, sandro.tosi, docs@python
2011-08-22 23:38:20eric.araujosetmessageid: <1314056300.6.0.0554640165983.issue12409@psf.upfronthosting.co.za>
2011-08-22 23:38:20eric.araujolinkissue12409 messages
2011-08-22 23:38:19eric.araujocreate