On May 23, 4:35 am, Scott SA <[EMAIL PROTECTED]> wrote: > It seems, the problem _can_ be in how PIL is installed into the site-packages > directory. > The alternative is that your environment (i.e. sys.path) does not contain the > correct path > to the correct python site-packages directory. I have multiple python > installations on my > system and not all packages are in each install. In my main Python, I have a > PIL > directory and a PIL.pth that points to the directory - it wasn't set up that > way in the > Python I was using with the Django install.
The path was the problem. My normal python is 2.4 and in that site- packages directory, a PIL.pth file siad "PIL". But, since PIL was installed using MacPorts, the PIL directory was under /opt/local... So, I edited the PIL.pth file in the python 2.4 site-packages directory. I changed it from looking for a PIL directory right there to looking for the PIL directory under /opt/local. PIL Changed to: /opt/local/lib/python2.4/site-packages/PIL And it works. Many thanks for all of your help and advice guys. Understanding how python uses site-packages to find modules has really helped me out. -- Austin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
