Log file Viewer

[06:07:25] <radix> so I just installed python 2.7.9 from homebrow, and I am trying to install/upgrade pip into my home directory. I had this working with the python built-in to OS X, but I'm having all sorts of trouble with it now

[06:08:24] <radix> first I had to comment out a "prefix=/usr/local" in a distutils.cfg, but now I'm getting the rather hilarious behavior of "pip install --user --upgrade pip" saying "Using cached pip-7.0.3-py2.py3-none-any.whl" and then, at the end, saying "Successfully installed pip-6.1.0".

[06:08:49] <radix> and, indeed, it seems to be installing pip-6.1.0 into my ~/Library/Python/2.7.

[06:10:14] <radix> oh, wait, hold on. no, I think the problem is that the pip python library in /usr/local is still taking precedent...

[06:11:19] <radix> at least the __init__.py has __version__ = "7.0.3", so that's good. Then the questions are: 1) why did pip say it installed 6.0.1, and 2) why isn't my sys.path set up properly, when this was working with the system-installed python...

[06:15:21] <radix> I guess system python just has that in my sys.path by default and the homebrew version doesn't.

[06:17:10] <radix> ah, no! the homebrew version does as well. but I see that my sys.path *explicitly* references pip-6.1.0-py27.egg *before* my ~/Library path. :-(

[06:25:53] <radix> alright. Got everything working after I hacked both distutils.cfg and an easy_install .pth file in /usr/local. D:

[06:36:45] <radix> (the sad thing is that my whole goal was to try not to change anything installed by my package manager and keep everything isolated to my home directory)

[16:27:29] <tdsmith> radix: pip is not always honest about the version it actually installs https://github.com/pypa/pip/issues/2642

[16:30:10] <tdsmith> putting eggs in the front of sys.path is a setuptoolsism; homebrew could install pip as a flat package i guess!

[16:31:21] <dstufft> tdsmith: does homebrew download the tarballs and setup.py install?

[16:31:52] <tdsmith> yes

[16:32:57] <dstufft> tdsmith: is there a reason you do that over just doing get-pip.py? (Not that it's wrong, jsut curious)

[16:33:18] <radix> tdsmith: oh, do you maintain the homebrew python thing? I was just looking for a repo or something to file a bug at

[16:35:33] <tdsmith> dstufft: Hmm, we've been doing it forever. Are there versioned get-pips somewhere that are promised not to change?

[16:35:55] <tdsmith> radix: that is my misfortune :) github.com/homebrew/homebrew/issues is the place

[16:35:59] <dstufft> tdsmith: ah no, get-pip.py isn't versioned at all, it just installs the latest

[16:36:32] <radix> so I guess I need to figure out what the bugs are to file. I had to do two things: get rid of a "prefix=/usr/local" line from a distutils.cfg, since it was conflicting with "--home"

[16:36:47] <radix> and then I also had to remove a pip egg from a .pth file so my home-directory-installed version could take precedence

[16:37:13] <radix> I guess those are two different bugs? it seems like the first one would prevent --home from ever working? or maybe installing pip is a special case

[16:37:56] <tdsmith> --home non-function is tracked: https://github.com/Homebrew/homebrew/pull/31811, https://github.com/pypa/pip/issues/2683

[16:38:10] <radix> oh cool, okay

[16:38:16] <dstufft> I think homebrew uses distutils.cfg with a prefix, and that breaks --home and --user and maybe some other things because distutils is bad

[16:38:42] <radix> then I'll just file the one about not being able to install a --user version of pip

[16:39:35] <dstufft> tdsmith: if you want to get pip and such installing as non eggs by default with homebrew I'm happy to help figure out the best way for homebrew to do that

[16:41:24] <tdsmith> i figure i just pass --single-version-externally-managed to setup.py, eh?

[16:44:28] <radix> filed it: https://github.com/pypa/pip/issues/2879

[16:44:39] <radix> that easy-install.pth file has some nasty sys.path mangling in it

[16:44:41] <radix> maybe that's the culprit

[16:45:03] <radix> ack crap

[16:45:07] <radix> I filed that in the wrong repo :P

[16:46:04] <dstufft> tdsmith: you also need --record install-record.txt (you might need a full path for that)

[16:46:32] <radix> tdsmith: so, I should file this in the main "homebrew" repo?

[16:47:03] <tdsmith> dstufft: :thumbsup:

[16:47:05] <tdsmith> radix: yes please!

[16:47:40] <radix> ok, here we go: https://github.com/Homebrew/homebrew/issues/40424

[16:48:11] <radix> that is a big ticket number. :)

[16:51:55] <tdsmith> yeah! homebrew depends on pull requests to stay up to date so we fly through numbers

[19:34:03] <agronholm> can somebody explain why "pip install -U typing" installs typing-0.0 from local cache instead of downloading the latest version?

[19:36:48] <agronholm> ahhh

[19:36:53] <agronholm> because it's marked beta

[20:12:57] <romangineer> Hi pippers!

[20:14:15] <romangineer> If I have a py project and wanted to be able to install it as a package via pip from a local repo, what kind of path would I take?

[20:16:14] <doismellburning> romangineer: https://packaging.python.org/en/latest/distributing.html + https://packaging.python.org/en/latest/mirrors.html iirc

[20:16:18] <doismellburning> oh not mirrors

[20:16:20] <doismellburning> er

[20:17:41] <romangineer> could local repo be done with devpi?

[20:21:13] <romangineer> looks like i should start with learning how to distrbute

[20:21:20] <romangineer> worry about local repo later

[21:31:42] <romangineer> I'm running a pip install for scipy on a vagrant instance, when it gets to "running setup.py install for scipy" it takes over 15 minutes. Anyone have an idea how to troubleshoot? Is there a way to get better logging for a pip install?

[21:34:02] <aclark> romangineer: and? scipy normally takes that long IIRC

[21:34:32] <aclark> romangineer: no output?

[21:36:11] <romangineer> I didn't know that. I'm not seeing any output during the install.

[21:37:07] <romangineer> Are there any ways to speed it up?

[21:38:50] <romangineer> I'll try pip verbose next time