[docs] [issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi report at bugs.python.org
Sat Jan 14 19:13:53 CET 2012

Sandro Tosi <sandro.tosi at gmail.com> added the comment:

On Sat, Jan 14, 2012 at 04:36, Éric Araujo <report at bugs.python.org> wrote:
> Éric Araujo <merwok at netwok.org> added the comment:
> 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.

thanks! I've just updated 2.7 to sphinx 1.0 - yay

> 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.

I just did that with:

> 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 :)

Ah yes, sure!



Python tracker <report at bugs.python.org>

More information about the docs mailing list