PMXBOT Log file Viewer

Help | Karma | Search:

#pypa logs for Monday the 8th of December, 2014

(Back to #pypa overview) (Back to channel listing) (Animate logs)
[11:57:03] <s1341> I've encountered some very strange behaviour in pip on osx
[11:58:24] <s1341> is this the right place to discuss this?
[12:01:13] <mgedmin> I think so, yes
[12:01:58] <s1341> awesome.
[12:02:43] <s1341> I'm installing additional instances of python using pyenv
[12:02:59] <s1341> (https://github.com/yyuu/pyenv)
[12:03:59] <s1341> pyenv installs pip using get-pip.py
[12:04:43] <s1341> this fails, because even though get-pip.py is executed by the new instance of python
[12:05:54] <s1341> when it tries to check whether pip is installed, it finds the pip in the system python '/Library/Python/2.7/site-packages'
[12:06:21] <s1341> and since pip is installed in the system python, it doesn't install pip
[12:06:43] <s1341> to reproduce:
[12:06:46] <s1341> 1. install pyenv
[12:07:01] <s1341> 2. install a new python: PYTHON_CONFIGURE_OPTS="--enable-framework" pyenv install 2.7.8
[12:07:28] <mgedmin> is PYTHONPATH set in your environment?
[12:07:29] <s1341> 3. enter the new python: pyenv shell 2.7.8
[12:07:45] <s1341> 4. try to run pip
[12:07:57] <s1341> mgedmin no. PYTHONPATH is not sest
[12:07:58] <s1341> set
[12:08:10] <mgedmin> in that case this looks like a bug in pyenv
[12:08:31] <s1341> i believe that it isn't .
[12:08:42] <s1341> i can try to reproduce without pyenv
[12:08:50] <mgedmin> hm
[12:09:23] <mgedmin> why would a pyenv-managed python try to access libraries from the system python's site-packages?
[12:09:30] <s1341> it shouldn't
[12:09:34] <s1341> but that's what pip is doing.
[12:09:45] <mgedmin> pip or get-pip.py?
[12:10:01] <s1341> when i manually install pip in the new python environment, i see similar behaviour for ANY package
[12:10:26] <s1341> if the package is installed in system python, the requirement is 'satisfied' even in the new python environment.
[12:10:50] <mgedmin> so somehow /Library ends up on sys.path
[12:11:08] <s1341> it is related.
[12:11:18] <s1341> because without it, everything seems to work.
[12:11:29] <mgedmin> why do you use it then?
[12:11:51] <s1341> It's necessary (sfaiu) so that other apps can dynamically link with the python.
[12:12:10] <mgedmin> hmm
[12:12:19] <mgedmin> this needs somebody with Mac-fu
[12:12:23] <s1341> yeah.
[12:12:38] <s1341> should i send this to the pip user or dev list?
[12:12:42] <mgedmin> maybe
[13:23:27] <s1341> mgedmin I managed to reproduce without pyenv
[13:23:46] <s1341> and I posted to the pip user group: https://groups.google.com/forum/#!topic/python-virtualenv/SOEfW7O3wiE
[15:17:43] <movi> i'm banging heads with pip and proxy
[15:18:00] <movi> /usr/local/bin/pip search --proxy="http://10.177.128.10:3128" lxml
[15:18:09] <movi> and it errors out. what am I doing wrong?
[15:20:35] <dstufft> can you be more specific? what does "errors out" mean in this context
[15:25:48] <movi> dstufft: http://pastebin.com/T8ZHNxzn
[15:25:58] <movi> it's funny, because install doesn't have a problem with proxy
[15:26:32] <dstufft> movi: oh, I missed this was search
[15:26:50] <dstufft> I don't think 1.5 has a working search w/ a proxy
[15:26:54] <dstufft> that's fixed in 6.0 I believe
[21:06:48] <buck11> install -e doesn't handle data_files ?