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 larry
Recipients georg.brandl, larry, ned.deily
Date 2014-05-04.20:30:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399235440.58.0.664596263354.issue21431@psf.upfronthosting.co.za>
In-reply-to
Content
3.4.1rc1 is the first release I've cut where the makefile didn't auto-download Sphinx.  And then the makefile used "python" and "sphinx-build" straight off the path, rather than finding the local ones.  To generate pydoc-topics, I had to do the following:

% ./configure --prefix=`pwd`/release && make
% ./release/bin/pip install sphinx
% cd Doc
% make pydoc-topics PYTHON=../release/bin/python SPHINXBUILD=../release/bin/sphinx-build

And apparently this didn't work.

Maybe there should be a "smoke test" to make sure pydoc-topics is okay?

And... maybe "make pydoc-topics" should copy the data file itself, rather than making me cut and paste paths out of PEP 101?  And *then* automatically test it?
History
Date User Action Args
2014-05-04 20:30:40larrysetrecipients: + larry, georg.brandl, ned.deily
2014-05-04 20:30:40larrysetmessageid: <1399235440.58.0.664596263354.issue21431@psf.upfronthosting.co.za>
2014-05-04 20:30:40larrylinkissue21431 messages
2014-05-04 20:30:40larrycreate