#6054: PIL import error
---------------------------------------------+------------------------------
Reporter: nesh | Owner: nobody
Status: reopened | Milestone:
Component: Validators | Version: SVN
Resolution: | Keywords: PIL
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by Keryn Knight):
Confirming that, under OSX 10.5.8, using easy_install to install either
1.16 or the more recent 1.1.7 release of PIL, django breaks in a couple of
ways. Specifically, I've been unable to use syncdb if I have an ImageField
present in any INSTALLED_APPS model. This is because, as others have
stated, Django only looks for a PIL package from which it can import the
Image module.
This is obviously, in itself, not a Django problem, but a easy_install/PIL
combination problem (its worth noting that using
[http://pip.openplans.org/ pip] to install PIL results in a PIL package in
site-packages), but it is somewhat of a show stopper for people who might
be beginning development, as, to their awareness, they have installed PIL
entirely correctly. Whether or not this is likely to affect production
scenarios, I don't know, but I support the suggestions & attempts to patch
the imports to look for Image ''et al'' in both locations outlined in the
original ticket.
--
Ticket URL: <http://code.djangoproject.com/ticket/6054#comment:9>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
