Message151264
| Author |
sandro.tosi |
| Recipients |
adam.woodbeck, brett.cannon, docs@python, eric.araujo, ezio.melotti, fdrake, georg.brandl, rhettinger, sandro.tosi, tshepang |
| Date |
2012年01月14日.18:13:52 |
| SpamBayes Score |
0.0011096229 |
| Marked as misclassified |
No |
| Message-id |
<CAPdtAj0JrhurNdB=u=UQURhC4PKTAcFAVVtErKMkJG9m2M4urQ@mail.gmail.com> |
| In-reply-to |
<1326512216.4.0.465598540602.issue12409@psf.upfronthosting.co.za> |
| Content |
On Sat, Jan 14, 2012 at 04:36, Éric Araujo <report@bugs.python.org> wrote:
>
> Éric Araujo <merwok@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:
http://mail.python.org/pipermail/python-dev/2012-January/115520.html
> 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!
Cheers,
Sandro |
|