PMXBOT Log file Viewer

Help | Karma | Search:

#pil logs for Tuesday the 30th of July, 2013

(Back to #pil overview) (Back to channel listing) (Animate logs)
[14:07:52] <yoav> Hey! I did some changes to Pillow and trying to test them
[14:08:17] <yoav> I'm trying to run PIL, but it fails with "ImportError: cannot import name _imaging"
[14:10:15] <yoav> Looks like setup.py is not building the C files. How do I build them? (I'm guessing the answer is not manually :) )
[14:11:24] <aclark> yoav: platform?
[14:11:35] <yoav> Ubuntu 13.04
[14:12:11] <aclark> if that is raring, you might try apt-get install python-imaging
[14:12:35] <aclark> and see if you get pillow
[14:12:38] <yoav> Not raring
[14:12:45] <aclark> k
[14:12:47] <aclark> in that case
[14:12:52] <aclark> install build-essentials
[14:13:01] <aclark> and python-pip and then pip install Pillow
[14:13:05] <aclark> that *should* work
[14:13:44] <yoav> I have Pillow installed, but I'm trying to test the modified Pillow version, inside a virtualenv
[14:15:07] <yoav> I also have build-essential installed
[14:47:02] <yoav> Nevermind, test on main Pillow install
[14:47:09] <yoav> s/test/tested/
[15:03:11] <_2xlp> I've been having trouble getting Pillow to work on OsX 10.6 , python 2.7.5 ; it won't recognize the _imaging c extensions. i saw some similar problems online, but mine seems weirder -- it works fine in a fresh virtualenv, but something seems to be conflicting in the virtualenv i need it in. does anyone have an idea on what to look for ?
[15:59:38] <_2xlp> after 3 hours of tests, it seems that there was something odd with the binary of python in the virtualenv. replacing it seems to work. done!
[20:05:44] <epicserve> wiredfool: did you see this, http://coreos.com/ ?
[21:39:04] <wiredfool> epicserve: I saw it, I haven't dug in to see exactly what they're doing