[issue10224] Build 3.x documentation using python3.x

Ezio Melotti added the comment: Éric, I think you should open a separate issue for this. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue10224] Build 3.x documentation using python3.x

Éric Araujo added the comment: Do we need to change Doc/Makefile to have “PYTHON = python3” or even “PYTHON = ./python” (so doctests run with the development version)? -- ___ Python tracker ___

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: Yep, thanks for the reminder. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue10224] Build 3.x documentation using python3.x

Ned Deily added the comment: For 3.4.1 and 3.5, the Doc/Makefile no longer explicitly vendors sphinx and its dependencies (via svn), rather it assumes that an externally-supplied sphinx-build is available, for example, via a venv and pip. And the current versions of sphinx and its dependencie

[issue10224] Build 3.x documentation using python3.x

Cherniavsky Beni added the comment: I was only thinking of 3.4, which will have venv and a pip bootstrapper. Is changing the doc build / doctest in scope for minor releases of 3.3 (or even earlier)? The commands I listed (using setup_distribute.py) also work with 3.3. (But they're unsecure -- h

[issue10224] Build 3.x documentation using python3.x

Brett Cannon added the comment: I guess if we are willing to write a mini-pip to download the latest release directly from PyPI we could. Since there are no C extensions we don't have to care about the lack of header files in Include if we are going to build from the repo build directly. Or ar

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: Ok, that sounds good then. BTW, for 3.3+ would it make sense instead to create a virtualenv and directly install the required versions from pypi? -- ___ Python tracker

[issue10224] Build 3.x documentation using python3.x

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue10224] Build 3.x documentation using python3.x

Ezio Melotti added the comment: Apparently they are cached, and unless the cache expires often, the server doesn't need to regenerate the tarball too often. However I don't know the details of the caching, and if they can be tweaked. -- ___ Python

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: A problem with using automatic tarballs from hg.python.org is that they take server load to generate, every time someone builds the docs from a new checkout. -- ___ Python tracker _

[issue10224] Build 3.x documentation using python3.x

Ezio Melotti added the comment: > Should I write a Makefile patch using the venv/install from pypi approach? > Or could somebody upload new versions to > http://svn.python.org/projects/external/? I looked at this issue over the past few days and discussed briefly with Georg about it. The 3 ma

[issue10224] Build 3.x documentation using python3.x

Cherniavsky Beni added the comment: After a lot of experimentation, this worked for me to build AND doctest using the local python: cd Doc/ ../python -m venv toolsenv curl http://python-distribute.org/distribute_setup.py | toolsenv/bin/python toolsenv/bin/easy_install pip toolsenv/bin/pip insta

[issue10224] Build 3.x documentation using python3.x

Zachary Ware added the comment: > Doc/make.bat assumes that this issue has already been resolved: > if "%PYTHON%" EQU "" set PYTHON=..\pcbuild\python > Even with '_d' appended, as it should be, that does not work for 3.x. > I think that line should be @rem'ed out until it does work. > Does anyo

[issue10224] Build 3.x documentation using python3.x

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue10224] Build 3.x documentation using python3.x

Terry J. Reedy added the comment: Doc/make.bat assumes that this issue has already been resolved: if "%PYTHON%" EQU "" set PYTHON=..\pcbuild\python Even with '_d' appended, as it should be, that does not work for 3.x. I think that line should be @rem'ed out until it does work. Does anyone mind

[issue10224] Build 3.x documentation using python3.x

Changes by Ezio Melotti : -- dependencies: +upgrade to sphinx 1.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue10224] Build 3.x documentation using python3.x

Brett Cannon added the comment: What exactly is blocking this? From looking on PyPI it seems Jinja2, Pygments, and Sphinx have all been ported to Python 3 at this point. Is it a matter of porting any custom code in Doc/ to Python 3 and then updating the Makefile to grab Python 3 versions of th

[issue10224] Build 3.x documentation using python3.x

Changes by Chris Jerdonek : -- nosy: +cjerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue10224] Build 3.x documentation using python3.x

Changes by Brett Cannon : -- versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10224] Build 3.x documentation using python3.x

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10224] Build 3.x documentation using python3.x

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10224] Build 3.x documentation using python3.x

Changes by Eric Snow : -- nosy: +ericsnow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue10224] Build 3.x documentation using python3.x

Sye van der Veen added the comment: When I built the documentation on Win7, it failed with a SyntaxError, and it took some digging to find the reason why. I was hoping that issuing this warning would save others the trouble. I agree: on Windows, PYTHON is rarely set. However, look in make.b

[issue10224] Build 3.x documentation using python3.x

Martin v. Löwis added the comment: Actually, on Windows, PYTHON is typically not set at all. So the likelihood of it being set to Python 3 is very low, unless you are trying to build Python documentation from time to time. Sye: I fail to see the point of your patch. sphinx-build.py already is

[issue10224] Build 3.x documentation using python3.x

Éric Araujo added the comment: > In either case, there's a high likelihood the PYTHON default will > resolve to 3.3a0 for any Python developer. Ah, I understand the reason for the phrasing in your patch: UNIX systems typically install 3.x as python3, not python, so the high likelihood is only

[issue10224] Build 3.x documentation using python3.x

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10224] Build 3.x documentation using python3.x

Sye van der Veen added the comment: I had trouble wording that sentence. Under Unix, Makefile is used, in which you specify "PYTHON=" on the command line else the default "python" (from the PATH) is used. Under Windows, it's make.bat, where PYTHON needs to be set in the environment else "..

[issue10224] Build 3.x documentation using python3.x

Éric Araujo added the comment: I don’t see how the comment “As such, you will need to specify PYTHON explicitly” logically follows from the fact that Python 2.x is required. IMO, building the docs require Python 2.x, so you’ll need a “python” executable on your PATH that is 2.x. --

[issue10224] Build 3.x documentation using python3.x

Sye van der Veen added the comment: I ran smack into this while setting up my Doc build for the first time. In trying to fix my build problems, it took me about an hour to find that this was a known issue. I've attached a patch to warn others of the issue, in the documentation and the build

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: I agree that 3.2 should eventually be independent of a 2.x Python. Since the "port to 3.x" part of Sphinx 1.1 is basically done, I might just do an early alpha release and use that for Doc/tools before 3.2 final. -- ___

[issue10224] Build 3.x documentation using python3.x

Alexander Belopolsky added the comment: 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 t

[issue10224] Build 3.x documentation using python3.x

Changes by Zbyszek Szmek : -- nosy: +zbysz ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue10224] Build 3.x documentation using python3.x

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue10224] Build 3.x documentation using python3.x

Alexander Belopolsky added the comment: > The usual build process via Makefile still uses Python 2, > and that won't change for 3.2. Would you consider changing "doctest" make target to check out sphinx trunk (or 3.x compatible release) and run it with the py3k python? This should not affect

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: (The usual build process via Makefile still uses Python 2, and that won't change for 3.2.) -- ___ Python tracker ___ ___

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: Nope, these files run just as fine in Python 2. -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue10224] Build 3.x documentation using python3.x

Martin v. Löwis added the comment: Did you know break building the 3.x documentation with Python 2? If so, please revert that change. -- nosy: +loewis ___ Python tracker ___ __

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: In r85910, I ported the Python-specific modules in tools/ so that they don't need to be 2to3-converted. Now you can basically easy_install Sphinx on 3.1 and run its sphinx-build without touching the Doc/ tree. -- __

[issue10224] Build 3.x documentation using python3.x

Georg Brandl added the comment: I fixed that bug in Sphinx rev 49747f5b0c70 (which I will push as soon as bitbucket is up again); incremental build now works for me. -- versions: +Python 3.3 -Python 3.2 ___ Python tracker

[issue10224] Build 3.x documentation using python3.x

Alexander Belopolsky added the comment: Incremental build was not that successful. After editing Doc/faq/programming.rst, I get the following in the error log: # Sphinx version: 1.1pre # Python version: 3.2a3+.0 # Docutils version: 0.7 release # Jinja2 version: 2.5.5 Traceback (most recent c

[issue10224] Build 3.x documentation using python3.x

Alexander Belopolsky added the comment: I had some success after running 2to3 on Doc/conf.py and Doc/tools. The build succeeded, but I have not compared the output yet. Running doctest, however, still reported lots of errors and hang in turtle.rst. $ sphinx-build -b doctest -d Doc/build3/d

[issue10224] Build 3.x documentation using python3.x

Changes by Alexander Belopolsky : -- assignee: -> d...@python components: +Build, Documentation nosy: +d...@python versions: +Python 3.2 ___ Python tracker ___ _

[issue10224] Build 3.x documentation using python3.x

Changes by Alexander Belopolsky : -- nosy: +eric.araujo, georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue10224] Build 3.x documentation using python3.x

New submission from Alexander Belopolsky : Opening a ticket to track the progress of getting python 3.x build its own documentation. So far I have installed Sphinx from http://bitbucket.org/birkenfeld/sphinx, but I get the following error: $ sphinx-build -b html -d Doc/build3/doctrees -D late