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 belopolsky
Recipients belopolsky, daniel.urban, docs@python, eric.araujo, georg.brandl, loewis, zbysz
Date 2010-11-08.16:12:43
SpamBayes Score 6.8742213e-07
Marked as misclassified No
Message-id <1289232779.54.0.416970122574.issue10224@psf.upfronthosting.co.za>
In-reply-to
Content
As discussed on #python-dev, building  3.x documentation using python3.x will require Sphinx 1.1 which will not be released in time for 3.2.

I am adding #10225 as a dependency because I feel that fixing actual errors in ReST doctests is more important than upgrading documentation tool chain.  Hopefully this will bring more eyes to that issue.

This said, I believe it is important for python-dev to "eat their own dogfood" and make 3.2 self-hosting.  In other words, if we want to convince users that 3.x is ready, we should not require 2.x in the build process.

Fortunately, Doc/tools is not shipped with python releases, so the transition can be made at any time regardless of python release schedule.
History
Date User Action Args
2010-11-08 16:12:59belopolskysetrecipients: + belopolsky, loewis, georg.brandl, eric.araujo, zbysz, daniel.urban, docs@python
2010-11-08 16:12:59belopolskysetmessageid: <1289232779.54.0.416970122574.issue10224@psf.upfronthosting.co.za>
2010-11-08 16:12:43belopolskylinkissue10224 messages
2010-11-08 16:12:43belopolskycreate