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 adam.woodbeck, brett.cannon, docs@python, eric.araujo, ezio.melotti, fdrake, georg.brandl, rhettinger, sandro.tosi, tshepang
Date 2012-01-14.03:36:54
SpamBayes Score 0.0050642323
Marked as misclassified No
Message-id <1326512216.4.0.465598540602.issue12409@psf.upfronthosting.co.za>
In-reply-to
Content
I just replied to your python-dev email.  I think you can update 2.7 to use Sphinx 1.0 as soon as you’re down to a handful of warnings.

When the migration is done, you can add the documenting doc to the devguide and send a message to pydev to tell people to not commit changes to Doc/documenting in CPython clones anymore.

In the same email you can ask who to ask for setting up redirects (BTW, will redirecting paths to fragments work?  e.g. docs.py.o/documenting/style to devguide/documenting#style-and-blah).  When the redirects are up you’ll be able to rm Doc/documenting.

Then we’ll open other reports to talk about the unrelated I mentioned and to see how to stop downloading Sphinx from svn once per clone :)
History
Date User Action Args
2012-01-14 03:36:56eric.araujosetrecipients: + eric.araujo, fdrake, brett.cannon, georg.brandl, rhettinger, ezio.melotti, sandro.tosi, docs@python, tshepang, adam.woodbeck
2012-01-14 03:36:56eric.araujosetmessageid: <1326512216.4.0.465598540602.issue12409@psf.upfronthosting.co.za>
2012-01-14 03:36:55eric.araujolinkissue12409 messages
2012-01-14 03:36:54eric.araujocreate