On Fri, Jan 29, 2016 at 18:28:53 -0500, Barry Warsaw wrote:
> I don't actually know whether Built-Using *does* anything useful[*], but IWBNI
> (maybe) some kind of notification or auto-rebuild happened. I don't think it
> does, but Donald's right. It's the same problem that Go or statically
Hi Barry,
Did you consider creating whl files at install time¹ rather than pip's
build time? This way whl can be regenerated whenever one of needed
packages is updated and there's no need to rebuild pip package.
[¹] using dpkg (file) triggers (/usr/share/doc/dpkg-dev/triggers.txt.gz)
--
Piotr
On Feb 01, 2016, at 03:01 PM, Piotr Ożarowski wrote:
>Did you consider creating whl files at install time¹ rather than pip's
>build time? This way whl can be regenerated whenever one of needed
>packages is updated and there's no need to rebuild pip package.
>
>[¹] using dpkg (file) triggers
On Jan 30, 2016, at 11:33 AM, Robert Collins wrote:
> If a new requests package is built, uploaded to the archive and
>apt-get installed on my machine, and I then do:
>virtualenv test
>. test/bin/activate
>pip install foobar
> ^--- what version of requests will be used by this in-virtualenv
I am confused. Here's my understanding of things...
- Pip doesn't need wheels at all - its vendoring technique doesn't use wheels.
- Virtualenv needs to install pip, wheel, setuptools when it makes a
new environment, and it does that by some oogly code
- venv might do the same thing, but I
> On Jan 29, 2016, at 5:33 PM, Robert Collins wrote:
>
> I am confused. Here's my understanding of things...
>
> - Pip doesn't need wheels at all - its vendoring technique doesn't use wheels.
> - Virtualenv needs to install pip, wheel, setuptools when it makes a
>
TL;DR By the end of today, I expect to upload pip 8.0.2 to unstable, finally
bringing us up to the latest version.
It's been a long slog, with many people helping out. I hope that all the hard
work done to get us here means it will be much, much easier to track new pip,
virtualenv, and pyvenv
7 matches
Mail list logo