I think this may be a bit of a misunderstanding in how to use PIL ...
PIL has a rather unusual packaging in which the PIL library is added to PYTHONPATH (and not to the directory containing it), so if you install using a simple installation, it will do something like:
/Lib /Lib/site-packages /Lib/site-packages/PIL-1.1.7-py2.6-win32.egg /Lib/site-packages/PIL-1.1.7-py2.6-win32.egg/Image.py
So, the import that actually needs to be done is: import the image as pilImage (i.e.: not in the PIL when importing).
Link confirming that this is how import should be: http://effbot.org/imagingbook/introduction.htm
And in this case, the directory added to PYTHONPATH should be: "/Lib/site-packages/PIL-1.1.7-py2.6-win32.egg"
Please note that your import may work if you renamed the /Lib/site-packages/PIL-1.1.7-py2.6-win32.egg directory to / lib / site- packages / PIL and just leave / lib / site- packages / in PYTHONPATH (in this case, you still need to go to setting up the PyDev interpreter and just click "apply" so that it finds that the new PIL package has been added to the PYTHONPATH note , which in this case is / Lib / site -packages / PIL should NOT be added to PYTHONPATH )
source share