Ned Deily added the comment: For the 3.6 and master branches, I've now enhanced Doc/Makefile to better find its tools. If the doc venv is present, e.g. make venv was run, the Doc build recipe will use sphinx-build and blurb from there, otherwise the process PATH will be search for installed versions. Hopefully, that covers nearly all use cases. But, if necessary, explicit locations for the tools can be set with the SPHINXBUILD and BLURB variables. 3.4 and 3.5 are now in security-fix mode: this change can be backported at their release manager's discretion. The 2.7 Doc/Makefile does not need to use blurb because its docset does not build a changelog html file like the 3.x docs do.
---------- priority: release blocker -> versions: -Python 2.7 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31036> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
