Log file Viewer

[02:30:39] <nedbat> how does pip find cached wheels in the ~/Library/Caches/pip tree? They are indexed by their hash, doesn't it need a way to get the hash before it has the wheel?

[10:55:39] <xafer> nedbat, pip keeps searching for suitable links like before cached wheel and only when it has selected its best link (for example, pypi.python.org/packages/py2.py3/D/Django/Django-1.8.3-py2.py3-none-any.whl) will it search for a cached wheel for this particular package link

[10:56:09] <xafer> the hash is computed from the found link, cf github.com/pypa/pip/blob/develop/pip/wheel.py#L66-L104

[10:57:09] <nedbat> xafer: so it's the hash of the url of the package used to make the wheel? it seems like wheels are cached only for kits that aren't wheels themselves

[10:58:40] <xafer> yes exactly, and wheel links are not cached in the wheel cache: github.com/pypa/pip/blob/develop/pip/wheel.py#L112-L113

[10:59:02] <xafer> (so my example with django wheel was pretty bad :p)

[11:00:06] <xafer> Direct wheel links are cached by the existing http cache pip uses.

[11:00:36] <nedbat> xafer: ok, that makes sense, thanks.

[11:02:13] <xafer> you're welcome

[11:04:37] <nedbat> xafer: since you have so much info, is there a supported way to flush that cache? I can delete files from it, but I have to know where it is on disk.

[11:07:11] <xafer> Not to my knownledge, cf github.com/pypa/pip/issues/2851

[11:12:35] <nedbat> xafer: thanks, i should get in the habit of looking through these issues.

[12:33:30] <dstufft> nedbat: we have a lot of them :/

[12:40:50] <nedbat> dstufft: yeah :(

[14:42:38] <yardenbar> Hi all, I've created a virtualenv under regular user and installed my packages to it. After executing 'workon myenv' I'm trying to execute a command from the package with sudo, but 'command not found', any idea?

[14:43:41] <yardenbar> Same result when passing -E to sudo -> sudo -E myCommand

[14:46:38] <chudler> How long has pypi.python.org been redirecting /simple to https? I just noticed it yesterday

[14:50:41] <dstufft> chudler: 2013? or so

[14:52:33] <chudler> Thank you dstufft. I was reading this channel logs here <chat-logs.dcpython.org/day/pypa/2014-03-27>; that *seem* to imply /simple is helpful for the situation having no HTTPS proxy, but I might misread that. No matter, I setup a CONNECT proxy for it today

[14:53:23] <dstufft> chudler: no problem :)

[14:53:41] <dstufft> In the future we won't redirect /simple/ from HTTP to HTTPS, we're going to be just returning an error on HTTP

[14:53:48] <dstufft> so it's good to switch yourself to https now if you're not

[16:05:05] <ronny> yardenbar: pass absolute paths, sudo cleans up the environment to avoid abuse, virtualenv env vars are probably under the false positives

[20:06:12] <wolever> How does pip determine when files are "externally hosted"?

[20:06:51] <wolever> Using pip install --index-url mysite.com/simple and I'm getting an "externally hosted" error, even though the packages are from the same host

[20:37:32] <dstufft> wolever: uhh

[20:37:35] <dstufft> PEP something

[20:37:39] <dstufft> sec

[20:39:08] <dstufft> python.org/dev/peps/pep-0438

[20:39:49] <nanonyme> Soon there's a PEP for everything

[20:41:15] <wolever> woo! Thanks!

[20:45:16] <wolever> okay! rel="internal" it is

[20:45:25] <wolever> I'm going to be pushing out a pip2pi update soon to fix that

[21:44:48] <_habnabit> can pip or any other tool force installed binaries to have a python version suffix? e.g. flake8 doesn't install flake8-2.7. pipsi seems like it would almost be appropriate here, but it doesn't support python 3 and doesn't do this explicitly

[21:47:43] <ronny> _habnabit: pipsi doesnt add python version prefixes yet and it supports python3

[21:47:56] <_habnabit> ronny, not the version on pypi

[21:49:08] <_habnabit> ronny, either way, pipsi doesn't solve this problem

[21:50:00] <ronny> _habnabit: pipsi supports python3 even in the pypi version, version prefixes are not added atm

[21:51:07] <_habnabit> ronny, ok, so the version released today supports it. anyway, do you know of a tool that does solve this problem?

[21:51:25] <ronny> _habnabit: 0.9 is ages old, 0.10 didnt add it

[21:51:45] <_habnabit> ronny, 0.9 says 'uploaded on 2015-08-12'

[21:52:11] <ronny> _habnabit: hmm wait

[21:52:51] <ronny> meh, i got onfused by the release a few minutes ago (i had 0.9 in my head for so long that i added 1 and wondered where it was

[21:55:19] <_habnabit> ronny, looks like the 'install into' merge request wasn't merged yet either

[21:56:12] <ronny> _habnabit: the install into one is a bit broken ^^

[21:57:41] <_habnabit> i don't know if i should hack this into pipsi or pip

[21:57:52] <_habnabit> better odds of landing it in pipsi at least

[21:59:16] <ronny> _habnabit: install_into needs a json file with some metadata per env tho

[21:59:24] <ronny> (its a middle-sized refactor)

[21:59:42] <_habnabit> ronny, you mean you want some way of keeping metadata per pipsi env?

[22:00:07] <ronny> _habnabit: yes, else pipsi update will be a bit in a pinch

[22:00:26] <ronny> also a remake comman o a clone command wont have any idea whats in there and with what settings

[22:00:40] <_habnabit> ronny, because you want pipsi update to be able to update things installed into?

[22:00:55] <ronny> yes, imagine stuff like tox and detox in a env

[22:01:11] <ronny> then tox updates a major and detox is fried ^^

[22:01:12] <_habnabit> ok

[22:01:36] <_habnabit> and there's nothing like that at all right now?

[22:01:43] <ronny> _habnabit: first step would be some plumbing commands (creation, installation, destruction, copying scripts)

[22:01:55] <ronny> yes, i never found the time to do it

[22:04:05] <ronny> _habnabit: could even be a file in XDG_CONFIG_HOME - but there needs to be some metadata (python version, installed packages, installed scripts)