On 19 January 2018 at 20:39, Victor Stinner <victor.stinner(a)gmail.com>
> 2018-01-19 11:28 GMT+01:00 Stefan Behnel <stefan_ml(a)behnel.de>:
> > That suggests adding Django 2 as a new Py3-only benchmark.
> Again, the practical issue is to install Django 2 and Django 1.11 in
> the same virtual environment. I'm not sure that it's doable.
> I would prefer to not have to create a different virtualenv for
> Python3-only dependencies.
> I needed to release quickly a bugfix release, fix --track-memory,
> feature asked by Xiang Zhang, so I released performance 0.6.1 which
> only updated Django from 1.11.3 to 1.11.9.
> Or we need to redesign how performance install dependencies, but
> that's a larger project :-)
It may be worth looking at using pew to set up a separate virtual
environment for each benchmark, but then use `pew add` to share common
components (like perf itself) between them. That way you won't have
conflicting dependencies between benchmarks (since they'll be in separate
venvs), without having to duplicate *all* the common components.
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia