#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 |
---------------------------------------------+------------------------------
Changes (by hozn):
* status: closed => reopened
* resolution: invalid =>
Comment:
(As other have noted) installing the latest (1.1.7) version of PIL using
{{{easy_install}}} results in the {{{from PIL import Image}}} failing
({{{import Image}}} works).
While I agree that this is probably a PIL packaging problem (or ambiguous
documentation on their part), from the perspective of making Django "just
work", it (Django) should really try both imports. This is a trivial
change and will make people who want to use setuptools to install Django
and dependencies far less frustrated. The current limitation means that
you can't just create a setup.py for your project with deps on Django and
PIL and expect it to actually work. For me that's enough to prohibit use
of ImageField.
--
Ticket URL: <http://code.djangoproject.com/ticket/6054#comment:8>
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.
