[Image-SIG] cannot import from PIL when easy_installed
Christian Zagrodnick
cz at gocept.com
Thu May 24 14:34:40 CEST 2007
Hi there
On 2007-02-04 20:54:09 +0100, Daniel Nouri <daniel.nouri at gmail.com> said:
>
> When you install PIL via easy_install, you cannot import from the PIL
> module. Is this a bug in PIL or in code that tries to import "from PIL"?
>
> >>> import PIL
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> ImportError: No module named PIL
> >>> import Image #no error
>
> This is how I install PIL:
>
> $ easy_install --find-links http://www.pythonware.com/products/pil/ \
> Imaging
>
> There is an open ticket in Plone for this
> http://dev.plone.org/plone/ticket/5883
Yes, it would be very nice if PIL got setuptools aware. The current
state not optimal. Escpecially because it *does* install but then is
not correctly installed. The setuptools integration is quite important
for automatically setting up a whole software bundle.
What happens on install is that PIL is not installed as a package but
its *contents* clutters the namespace. So you get to import Image
instead of PIL. But you also could just `import ArgImagePlugin` like
you'd `import sys`.
So, is anybody taking care of this?
--
Christian Zagrodnick
gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale
www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
More information about the Image-SIG
mailing list