PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Tuesday the 26th of May, 2015

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[11:38:10] <pjdelport> Ahoy
[11:38:51] <pjdelport> The pip 7 changelog says: "No longer implicitly support an insecure origin origin"
[11:39:11] <pjdelport> Is that an accidental doubling, or is "origin origin" a technical term? :)
[12:08:21] <pjdelport> Also, is there anything magical that needs to be done to enable pip 7's new wheel caching?
[12:08:36] <ronny> pjdelport: wheel caching is enabled by default
[12:08:39] <pjdelport> I upgraded to pip 7, but it doesn't seem to be caching the built wheels.
[12:08:52] <pjdelport> It's still building packages from source every time.
[12:08:57] <ronny> pjdelport: does for me for sure, you might suffer from a cold cache
[12:09:15] <ronny> how do you download/build the packages?
[12:09:30] <pjdelport> Just "pip install Pillow"
[12:09:33] <pjdelport> (for example)
[12:09:54] <ronny> pjdelport: that took a while the first time i did it, and was instant the second time
[12:10:07] <pjdelport> The normal HTTP cache is being used, but there's no wheel cache that I can see.
[12:10:15] <pjdelport> No mention in the log, either.
[12:10:22] <pjdelport> This is with pip 7.0.1
[12:10:48] <pjdelport> Logging verbosely, it's definitely doing the C compilation from source each time.
[12:11:07] <pjdelport> The wheel cache is supposed to go in ~/.cache/pip/wheels, if I understand right?
[12:11:22] <pjdelport> That's not being created.
[12:12:19] <ronny> its for me
[12:12:22] <ronny> what platform?
[12:12:33] <pjdelport> Ubuntu 15.04
[12:12:55] <ronny> did you install the wheel tool together with pip?
[12:13:23] <pjdelport> Oh, no, this is just with a temporary virtualenv for testing.
[12:13:31] <pjdelport> So it needs wheel separately installed?
[12:13:48] <ronny> i recall its required
[12:13:55] <pjdelport> Ah, now it seems to be doing something.
[12:13:58] <ronny> but the latest virtualenv installs all of them
[12:14:18] <pjdelport> Okay, that explains it.
[12:20:33] <pjdelport> I'm using Ubuntu's python-virtualenvwrapper packages, which doesn't install wheel automatically.
[12:22:47] <ronny> pjdelport: i suspects its jsut outdated - isnt there a ppa with latest python stuff?
[12:23:22] <pjdelport> Probably, but I'm not going to futz around with a PPA for that. :)
[12:23:52] <pjdelport> Easy enough to add "pip install wheel" to my ~/.virtualenvs/postmkvirtualenv for now.
[12:43:13] <pjdelport> Looks like it's working pretty well so far!
[12:43:14] <pjdelport> Awesome.
[12:43:43] <pjdelport> I've been using a manual wheelhouse cache until now, but this will be a lot easier for our whole team to manage.
[22:30:39] <xafer> hello dstufft, I've just noticed https://github.com/pypa/pip/pull/2387 is a PR and not an issue, maybe we should have an issue open ?
[22:30:54] <dstufft> oh
[22:30:55] <dstufft> heh
[22:31:24] <dstufft> that's what I get for just blindly listening to you xafer !!!
[22:31:26] <dstufft> :)
[22:31:30] <dstufft> yea probably makes sense
[22:31:31] <dstufft> I'll reopen
[22:31:46] <xafer> Yup, third issue closed that way ^^
[22:32:49] <xafer> regarding this issue I first went with https://github.com/xavfernandez/pip/commit/9973c702730938e68e69639d3c8c5509ddd7e3c7
[22:33:21] <xafer> but this doesnt catch all "pip install pip==7.0.1" and other possibilities
[22:34:26] <xafer> maybe the simplest solution would be to perform the check after the run call ?
[22:34:49] <xafer> if pip has updated itself in the meantime, it will have nothing to report ?
[22:35:10] <dstufft> xafer: that's not a bad idea, it's also more likely to be noticed if it's at the end instead of the beginning probably
[22:37:18] <dstufft> xafer: it also doesn't involve the hacks like scanning sys.argv for "pip", which I like better about it too :)
[22:37:41] <xafer> ok, I'll make a PR and sleep on it :)
[22:45:47] <xafer> done, good night :)