Log file Viewer

[00:15:34] <jessamy__> writing test cases for virtualenvwrapper is certainly showing me interesting things about virtualenv

[17:02:56] <apollo13> dstufft: https://dpaste.de/UFsF/raw :(

[17:02:58] <apollo13> ideas?

[17:09:51] <isthisreallife> https://dpaste.de/Bfwd why pip list doesnt work?

[17:13:10] <jessamynsmith> isthisreallife: what version of pip?

[17:14:14] <isthisreallife> 1.1

[17:15:35] <jessamynsmith> I'd do "pip install -U pip" if I were you

[17:17:23] <isthisreallife> thank you

[17:20:42] <ronny> re

[17:20:48] <ronny> dstufft: ping?

[17:22:32] <ronny> apollo13: looks like the enum pacakge thats being installed does not fir the stdlib one anymore and the stdlib started using it

[17:22:49] <apollo13> ronny: right, but that is a bit ugly imo *gg*

[17:23:01] <ronny> apollo13: and the local file masking the stdlib breaking it

[17:23:14] <apollo13> ronny: but doesn't 3.4 prefer stdlib file imports?

[17:23:17] <ronny> apollo13: there is no easy fix for that, its a bug in the enum34 packge

[17:24:27] <ronny> apollo13: as far as i can tell it does self-import in setup.py,

[17:24:34] <apollo13> *sigh*

[17:26:02] <apollo13> interestingly enough only I seem to have this problem on debian :)

[17:26:05] <ronny> ah, its not self-immporting, but pythonpath operations kill it

[17:26:19] <ronny> apollo13: ah, and debian likes to break the import system

[17:26:37] <apollo13> ?

[17:26:42] <apollo13> I doubt that this is debians fault now :þ

[17:27:35] <ronny> apollo13: when it works on other distros on python 3.4 its likely a debian patch for extra import paths and other details

[17:27:38] <apollo13> btw should it be possible to create a python3 venv using virtualenv from python2 when specifying -p /usr/bin/python3.4

[17:27:49] <ronny> yes

[17:27:53] <ronny> i do that all the time

[17:27:53] <apollo13> >>> sys.path

[17:27:54] <apollo13> ['', '/usr/lib/python3.4', '/usr/lib/python3.4/plat-x86_64-linux-gnu', '/usr/lib/python3.4/lib-dynload', '/usr/local/lib/python3.4/dist-packages', '/usr/lib/python3/dist-packages']

[17:27:57] <apollo13> see sane enough

[17:28:00] <isthisreallife> https://dpaste.de/Njmm

[17:28:05] <isthisreallife> how to fix this?

[17:28:09] <ronny> apollo13: '' is the problem ^^

[17:28:29] <apollo13> ronny: I get https://dpaste.de/aSSq/raw when I try that

[17:28:37] <apollo13> ronny: mhm

[17:28:42] <apollo13> wonder how that gets there

[17:28:46] <ronny> isthisreallife: you need development headers for postgresql and a compiler

[17:29:59] <ronny> apollo13: the same works for me on fedora

[17:30:11] <apollo13> ronny: and your sys.path misses '' there?

[17:31:04] <ronny> apollo13: nope

[17:31:06] <ronny> bbl, dinner

[17:31:27] <apollo13> https://github.com/pypa/virtualenv/issues/671

[17:32:09] <jessamynsmith> I spent all of yesterday making sure virtualenvwrapper handles spaces in the path correctly... so now you can make a virtualenv with a space in the name (why you'd want to, I don't know) but then pip is super unhappy.

[17:35:28] <jessamynsmith> https://gist.github.com/anonymous/ea90c0ee95e79f75ad0e

[17:35:30] <jessamynsmith> poor pip

[17:39:37] <isthisreallife> ronny, so i need to install libpq-dev? its already installed.

[17:39:42] <isthisreallife> im so confused

[17:54:10] <isthisreallife> hmm

[17:58:40] <isthisreallife> okay apt-get install python-dev solved problem

[17:59:36] <isthisreallife> or bunch of other commands i copied from stackoverflow

[17:59:50] <isthisreallife> but it works now