pmxbot IRC Log Viewer

[22:02:12] <tsurantino> anybody online that can assist me with the installation of Pillow? http://dpaste.com/1227007/

[22:02:26] <tsurantino> I am trying to use it with Django but am running into The _imaging C module is not installed

[22:15:52] <aclark> tsurantino: can you paste the error?

[22:16:16] <tsurantino> aclark: http://dpaste.com/1227047/

[22:16:43] <aclark> tsurantino: remove PIL first, then install Pillow

[22:16:57] <aclark> (that is PIL erroring, not Pillow)

[22:17:23] <tsurantino> but I don't have PIL installed, that's the thing

[22:18:37] <tsurantino> this is my requirements.txt, I just did a freeze

[22:18:37] <tsurantino> http://dpaste.com/1227049/

[22:19:10] <aclark> tsurantino: humor me and pip uninstall PIL (something could have required it)

[22:19:33] <tsurantino> Cannot uninstall requirement pil, not installed

[22:19:34] <tsurantino> Storing complete log in /Users/arturtsurkan/.pip/pip.log

[22:19:40] <aclark> k

[22:19:54] <aclark> tsurantino: and you have a Pillow in site-packages too?

[22:20:20] <aclark> tsurantino: obviously the error you are getting shouldn't happen :-)

[22:20:34] <tsurantino> aclark: which is the *worst* kind of error

[22:20:48] <tsurantino> I have Pillow-2.0.0-py2.7.egg-info

[22:20:51] <tsurantino> and I have PIL

[22:21:07] <aclark> tsurantino: does this fail: >>> image Image ?

[22:21:14] <tsurantino> it does

[22:21:14] <aclark> errr, >>> import Image

[22:21:16] <aclark> ok

[22:21:19] <tsurantino> wait

[22:21:19] <tsurantino> sorry

[22:21:20] <tsurantino> one second

[22:21:34] <tsurantino> I do python -v

[22:21:39] <tsurantino> import Image is no good

[22:21:42] <aclark> k

[22:21:43] <tsurantino> from PIL import Image is OK

[22:21:48] <tsurantino> and in my site-packages folder

[22:21:48] <aclark> right, that's good

[22:21:50] <tsurantino> I have the *.so files

[22:22:39] <aclark> so no PIL installed… but _imaging errors…

[22:22:39] <tsurantino> so it's like site-packages/_imaging.so and site-packages/PIL etc.

[22:23:00] <aclark> so how do you produce the error?

[22:23:49] <tsurantino> well, I'm using django-ckeditor and I am trying to upload an image - upon doing so it throws that error

[22:24:15] <tsurantino> I'm not sure if that's specific enough, so I can investigate further if it will help

[22:24:31] <wiredfool_> how are you installing pillow?

[22:24:35] <aclark> interesting

[22:24:39] <aclark> wiredfool_: pip

[22:25:22] <aclark> or trying to :-)

[22:25:32] <wiredfool_> can he checkout head with something similar to those git lines?

[22:26:15] <aclark> probably though I'm wondering why >>> from PIL import Image does not produce the error…

[22:27:07] <aclark> tsurantino: try replacing Pillow with -e git+git://github.com/python-imaging/Pillow.git#egg=Pillow just for kicks

[22:27:31] <aclark> maybe master fixes the error we don't know yet :-)

[22:27:39] <wiredfool_> so, it's working for you? and not for him?

[22:27:46] <wiredfool_> with the same requirements.txt?

[22:28:04] <tsurantino> I'm going to try that

[22:28:12] <aclark> wiredfool_: no, i haven't tested…

[22:28:17] <tsurantino> and if it doesn't work, I'm going to try the same with django-ckeditor

[22:28:30] <aclark> wiredfool_: but asked tsurantino to try >>> from PIL import Image

[22:28:43] <aclark> tsurantino: from PIL import Image does not produce an error, right?

[22:28:50] <tsurantino> no

[22:29:08] <aclark> so that would suggest "bad django env"… if such a thing could exist in this case

[22:29:11] <wiredfool_> so what's Image.__file__

[22:29:19] <wiredfool_> and what Image.core.__file__

[22:29:38] <wiredfool_> and just watch them to be some cross-virtualenv thing

[22:31:20] <tsurantino> So install pillow from head

[22:31:21] <tsurantino> was no good

[22:31:58] <aclark> tsurantino: yeah, didn't think so

[22:32:34] <wiredfool_> yeah, but head is namespaced, so it should all be in the PIL directory, even the _*.so files

[22:32:50] <aclark> wiredfool_: it does smell of cruft…

[22:33:01] <aclark> ok maybe remove cruft from site-packages then install head

[22:33:10] <tsurantino> cruft?

[22:33:16] <wiredfool_> is there a dist-packages?

[22:33:53] <tsurantino> where would that be located?

[22:34:16] <wiredfool_> next to site-packages

[22:34:25] <tsurantino> there is not

[22:35:44] <aclark> tsurantino: what OS?

[22:35:50] <tsurantino> mountain lion

[22:36:00] <aclark> tsurantino: cruft == bad env

[22:36:16] <aclark> tsurantino: how about brew install python and use that python instead of the OS python…

[22:37:01] <tsurantino> hold on, why would I need to do that even with virtualenv?

[22:37:24] <aclark> tsurantino: because the OS python sucks (you may also want brew to install some of PIL's deps e.g. libjpeg)

[22:37:55] <tsurantino> hmm, but then how would that work if I were to deploy to heroku (i.e., if I am specifically installing stuff for it to work with my OS)

[22:38:20] <aclark> tsurantino: brew installs a "clean" python, it's a package manager

[22:38:26] <aclark> nothing to do with heroku

[22:38:33] <tsurantino> but then what about libjpeg?

[22:38:56] <aclark> tsurantino: what about it? you need those deps wherever you are if you want PIL to work

[22:39:10] <tsurantino> okay fair, sorry, I am new to this so I'm just trying to put it in perspective

[22:39:15] <tsurantino> thank you so much for your help thus far

[22:39:30] <aclark> tsurantino: heroku is just ubuntu… i think you can specify deps there too, somehow

[22:39:34] <aclark> tsurantino: np

[22:41:30] <tsurantino> after installing python, what next?

[22:46:04] <aclark> tsurantino: use that python instead of the OS python

[22:50:47] <tsurantino> wicked

[22:50:49] <tsurantino> it works now

[22:50:59] <tsurantino> aclark you are the greatest human being on the planet

[22:51:18] <tsurantino> http://aclark.net/ if this is you

[22:51:21] <tsurantino> you deserve a gold star

[22:51:22] <tsurantino> if not

[22:51:25] <tsurantino> you still deserve a gold star

[22:51:37] <tsurantino> now I have the headache of putting this on S3, but I should be OK

[22:52:04] <aclark> tsurantino: hah, glad to hear!

[22:52:17] <aclark> that is me

[23:03:05] <wiredfool_> at least his googling found something created this century

[23:03:32] <aclark> heh

[23:09:38] <aclark> is this supposed to support python setup.py develop --enable-foo ? or is that wishful thinking

[23:11:33] <wiredfool_> I think so

[23:11:43] <wiredfool_> I think it means that foo is required

[23:12:08] <wiredfool_> and now that I say it, I think that perhaps we should replace enable with require

[23:14:46] <aclark> now i see, it works with the build_ext command only

[23:16:18] <aclark> wiredfool_: yeah, and features doesn't make sense either :-)

[23:16:32] <aclark> replace ALL the terminology

[23:16:54] <wiredfool_> let's just start with being careful about what we introduce

[23:17:14] <aclark> we haven't introduced anything yet

[23:17:33] <aclark> i'm not convinced i would use this… maybe someone else would though

[23:17:36] <wiredfool_> incidentally, apart from the tech aspects of the ico thing, I think we should be careful about the licence. It's compatible, but it probably would require a pointer/callout from the readme somewhere

[23:17:50] <aclark> the ico license?

[23:17:57] <wiredfool_> it's apache

[23:18:05] <aclark> aha

[23:18:11] <wiredfool_> not the pythonlike one that is the rest of

[23:18:14] <wiredfool_> PIL

[23:18:21] <aclark> are we considering supporting ico?

[23:18:39] <wiredfool_> there's a pull request, and the existing support looks flakey

[23:18:44] <aclark> ah ok

[23:18:55] <wiredfool_> apart from the general flakiness of the format itself

[23:19:36] <aclark> are we using code from the ico project or something? I'm not sure how supporting a format would require a license

[23:19:53] <aclark> unless we link to a lib or something

[23:20:10] <wiredfool_> The pull request is a rewrite of some other person's icoimageplugin

[23:20:18] <wiredfool_> fixing bugs in ours

[23:20:23] <aclark> oic

[23:21:10] <aclark> why does github think pillow has 13 issues? seems like a bug

[23:21:19] <wiredfool_> and porting other dude's to py3k

[23:21:31] <aclark> 8 open, 225 closed… 13?

[23:21:41] <wiredfool_> refresh

[23:21:43] <wiredfool_> I count 13

[23:27:12] <aclark> so weird, anon shows 13 too, but I see 8

[23:27:29] <aclark> oh, i had to clear milestones

[23:31:12] <aclark> wiredfool_: i think i'll just contact 2008 Bryan Davis <casadebender+pil@gmail.com> and ask if we can relicense

[23:32:00] <aclark> not that the PIL standard license really means anything to me…

[23:35:18] <wiredfool_> well, it's the legal framework for the whole fork

[23:35:37] <aclark> True

[23:35:52] <wiredfool_> and before 2.1, we should probably add additional copyrights

[23:36:11] <wiredfool_> as there's been large bits added

Log file Viewer

Help | Karma | Search:

#pil logs for Monday the 10th of June, 2013