Does anyone have any insights on how to work around the bug noted in #7019?
I need to add/edit a path somewhere, yes? But where? On May 20, 12:42 am, Austin Govella <[EMAIL PROTECTED]> wrote: > It was a PYTHONPATH problem. I fixed it using this tutorial: > *http://emmby.blogspot.com/2008/05/installing-python-pil-on-mac-os-x-1... > > (I'm using python 2.4, so I adjusted the path accordingly.) > > Everything validates. Server runs with no ImageField errors, but now > we get a new ImportError: "No module named ImageFile". > > That error corresponds to the closed ticket, #7019: > http://code.djangoproject.com/ticket/7019 > > Mr. Treddinick writes MacPorts doesn't correctly installPILon os x > 10.4: > > "This isn't a problem with Django. It's a problem with the wayPILis > installed and should be reported to the packager for fixing.PIL > should be installed so that thePILdirectory is part of the Python > module search path (normally done via aPIL.pth file) and thus import > ImageFile must work; otherwise it's installed incorrectly." > > Does anyone know how to fix this? What path should I add/edit where? > > (And as an aside, I read somewhere that the proper way to import Image > and ImageFile is to say "fromPILimport ImageFile". This works, but > "import ImageFile" doesn't. Is Django importing incorrectly?) > > Many thanks for any tips, > -- > Austin Govella --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
