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