PIL not found by plone when installed as an egg

[brcwhit]

"import PIL" is a sideffect of installing PIL via distutils. easy_install install Image etc as toplevel packages.

[dreamcatcher]

Can you be more specific? PIL comes with the installer. What is the issue?

[ianb]

PIL is installed so that all its modules become top-level modules. E.g., you can do import Image instead of from PIL import Image -- PIL ends up being a package because distutils lets you be vague about how you setup modules. But setuptools does not let you be vague in this way, so it only sets up the top-level packages as indicated in PIL's setup.py

[dreamcatcher]

So what is the issue?

• Is it that the installer is doing the wrong thing?
• Is it a bug in PIL's setup.py?
• Is it a bug in the way Plone is importing PIL?
• Do you get a traceback?

[ianb]

This is a bug in the way PIL is imported in Plone.

[ianb]

Here's all the files with PIL package references:

CMFPlone/MembershipTool.py
CMFPlone/utils.py
CMFPlone/MigrationTool.py
ATContentTypes/config.py
Archetypes/Field.py
CMFPlone/setup/dependencies.py
ATContentTypes/lib/imagetransform.py
ATContentTypes/configuration/datatype.py
PortalTransforms/libtransforms/piltransform.py

[limi]

Should be corrected in Plone 3.0 (or in 2.5.x if we can do it without any side effects).

Ian, do you need commit privileges to Plone and the Collective? I assume this is an easy fix for the people that know how. :)

[nouri]

Fixed in r12150

[nouri]

My fix in r12150 exposes another problem. As Sidnei pointed out, there is a top-level Image in Zope, so they conflict when you're unlucky.

Anyone have an idea of how to fix this? I desperately want PIL to be easy_installable for Plone.

[optilude]

Is the problem not PIL? It seems pretty lame to me that it should spam the top level namespace with things as common as Image (equally lame of Zope, of course).

I would much rather do 'from PIL import Image' than 'import Image'.

[hannosch]

I agree with Martin that this is a bug in the PIL egg and not in Plone.