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

Éric Araujo report at bugs.python.org
Sat Jan 14 04:36:56 CET 2012


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

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

----------
versions: +Python 2.7, Python 3.2, Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12409>
_______________________________________


More information about the docs mailing list