On Mon, Mar 4, 2013 at 3:20 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 4 March 2013 20:00, Daniel Holth dho...@gmail.com wrote:
On Mon, Mar 4, 2013 at 2:41 PM, Paul Moore p.f.mo...@gmail.com wrote:
In thinking about how virtualenv would describe the packages it wants
to preload in PEP 426
On 6 Mar 2013 00:59, PJ Eby p...@telecommunity.com wrote:
On Mon, Mar 4, 2013 at 3:20 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 4 March 2013 20:00, Daniel Holth dho...@gmail.com wrote:
On Mon, Mar 4, 2013 at 2:41 PM, Paul Moore p.f.mo...@gmail.com wrote:
In thinking about how virtualenv
In thinking about how virtualenv would describe the packages it wants
to preload in PEP 426 metadata form, it occurred to me that there are
scenarios with setuptools and distribute where it's not obvious how to
state the requirement you want. Specifically, if you want to install
setuptools if it
On Mon, Mar 4, 2013 at 2:41 PM, Paul Moore p.f.mo...@gmail.com wrote:
In thinking about how virtualenv would describe the packages it wants
to preload in PEP 426 metadata form, it occurred to me that there are
scenarios with setuptools and distribute where it's not obvious how to
state the
On 4 March 2013 20:00, Daniel Holth dho...@gmail.com wrote:
On Mon, Mar 4, 2013 at 2:41 PM, Paul Moore p.f.mo...@gmail.com wrote:
In thinking about how virtualenv would describe the packages it wants
to preload in PEP 426 metadata form, it occurred to me that there are
scenarios with
On Mon, Mar 4, 2013 at 2:41 PM, Paul Moore p.f.mo...@gmail.com wrote:
In thinking about how virtualenv would describe the packages it wants
to preload in PEP 426 metadata form, it occurred to me that there are
scenarios with setuptools and distribute where it's not obvious how to
state the
