On 2014-01-05 12:17:41 -0500 (-0500), Sean Dague wrote:
> Well that's really unfortunate.
>
> So if I understand that correctly there is *no* way to configure tox
> + pip to:
>
> * use site packages if they are sufficient to requirements.txt
> * install packages into venv if they are not (i.e.
On 01/05/2014 11:25 AM, Jeremy Stanley wrote:
On 2014-01-05 10:47:22 -0500 (-0500), Sean Dague wrote:
[...]
It seems like requirements should be sufficient. Forcing -U to the
latest all the time seems like it would actually mask a ton of
problems, and makes sitepackages = True to be largely usel
On 2014-01-05 10:47:22 -0500 (-0500), Sean Dague wrote:
[...]
> It seems like requirements should be sufficient. Forcing -U to the
> latest all the time seems like it would actually mask a ton of
> problems, and makes sitepackages = True to be largely useless.
[...]
In fact, I believe it was mostl
Excerpts from Sean Dague's message of 2014-01-05 07:47:22 -0800:
> While waiting some inordinate amount of time to compile lxml for a
> tempest pep8 test, I started to wonder why is it that we are using -U on
> all our pip install commands in tox (it's a pretty common pattern across
> projects).
On Sun, 2014-01-05 at 10:47 -0500, Sean Dague wrote:
> While waiting some inordinate amount of time to compile lxml for a
> tempest pep8 test, I started to wonder why is it that we are using -U on
> all our pip install commands in tox (it's a pretty common pattern across
> projects).
>
> It see
