[10:36:25] <mgedmin> having experienced the joy of a directory full of zipped egg files back with setuptools + zc.buildout, I can't fathom why anyone would want to replicate that experience using pip + wheels
[10:37:18] <mgedmin> no ctags, no recursive grep, no source code in stack traces (ok, this was fixed in python 3.x), no source code in pdb (also fixed in 3.x)
[11:44:53] <ronny> mgedmin: i have masses of virtualenvs, that each get copies of all package files, i really just want a repository that contains the importable packages and allows the envs to refer to those instead of installing local copies
[12:02:17] <mgedmin> ronny, I see your point -- this is in fact why I still use zc.buildout, because the shared egg cache is awesome
[12:02:33] <mgedmin> but it works with extracted directory trees just as well (if not better) as with zipped files
[12:07:59] <ronny> mgedmin: i see, so extracted it is
[15:34:33] <ejb> Does pip somehow link packages installed with -e git+... to the site-packages directory? I installed one such package and I had to add $VENV_DIR/src/the-package to my PYTHONPATH. In the past I've used other installed-from-git packages and only had to add $VENV_DIR/lib/python2.7/site-packages to my PYTHONPATH
[17:13:02] <icio> ejb: are you activating the virtual environment before running pip?
[17:13:19] <icio> `which pip` should return $VENV/bin/pip
[17:52:20] <ejb> icio: I got it working. I think that the -e option was part of the problem. I just uninstalled the package then reinstalled without -e
[20:57:41] <ronny> jaraco: is there a channel where its good to discss the irc package?
[20:58:53] <jaraco> ronny, not in particular - shall we create one?