You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This duplicates a part of bpo-10224, which proposes to upgrade all of Sphinx, Jinja2, and Pygments to Python 3 compatible versions (so we can build docs with Py3). In msg175768, Brett claims that all three have such versions.
Chris, if you want to push to only upgrade Sphinx and not the other two, you can re-open. But I'd like to see a justification as I suspect that upgrading the other two will, if anything, be easier (assuming no breakage of current usage).
Activity
cjerdonek commentedon Nov 14, 2012
This issue is to upgrade Python's Sphinx from version 1.0 to 1.1.
I don't already see an issue for this, and I'm not sure what upgrading entails.
Personally, I'm interested in the enhanced indexing capabilities, e.g. the "see" and "seealso" entry types, as well as marking main index entries:
http://sphinx-doc.org/markup/misc.html#directive-index
I'm sure other reasons for upgrading have been floated, though I don't know what they are.
vstinner commentedon Nov 16, 2012
According to the changelog, Sphinx 1.1 now supports Python 3. Cool!
Doc/Makefile may be modified to use "PYTHON = python3".
ezio-melotti commentedon Mar 14, 2013
When this is done make.bat should be updated too.
terryjreedy commentedon Mar 15, 2013
This duplicates a part of bpo-10224, which proposes to upgrade all of Sphinx, Jinja2, and Pygments to Python 3 compatible versions (so we can build docs with Py3). In msg175768, Brett claims that all three have such versions.
Chris, if you want to push to only upgrade Sphinx and not the other two, you can re-open. But I'd like to see a justification as I suspect that upgrading the other two will, if anything, be easier (assuming no breakage of current usage).