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 cjrh
Recipients cjrh, docs@python, ned.deily, willingc, zach.ware
Date 2017-11-27.21:23:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <F0936CA8-62F4-41CB-83F3-8BB98401A6A7@gmail.com>
In-reply-to <1511817166.79.0.213398074469.issue30487@psf.upfronthosting.co.za>
Content
Hi Ned

It's still supposed to allow both. It sounds like it's not working properly. I'll have a look. FYI, I worked on this for Zach Ware who is the primary stakeholder for this feature. 

Rgds
Caleb

> On 28 Nov 2017, at 7:12 AM, Ned Deily <report@bugs.python.org> wrote:
> 
> 
> Ned Deily <nad@python.org> added the comment:
> 
> I don't think this is a good idea. It has already caused problems with one buildbot (Issue32149) and will likely break other build scripts.  As the Doc Makefile stood previous to this commit, the Doc builds could take advantage of either a system-installed or user-supplied Sphinx and blurb without having to use the venv step.  Unless there are major objections, I am going to at least temporarily revert it.
> 
> ----------
> nosy: +ned.deily
> resolution: fixed -> 
> stage: resolved -> needs patch
> status: closed -> open
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue30487>
> _______________________________________
History
Date User Action Args
2017-11-27 21:23:33cjrhsetrecipients: + cjrh, ned.deily, docs@python, zach.ware, willingc
2017-11-27 21:23:33cjrhlinkissue30487 messages
2017-11-27 21:23:33cjrhcreate