On 27 févr. 2013, at 21:40, Marijonas Petrauskas <[email protected]> wrote:
> Why isn't Pillow the recommended Django image library yet? PIL has > been unmaintained for almost 3 years and has a number of annoying bugs > (e.g. fails to open some valid JPEG files, maybe has some security > issues as well). Pillow, on the other hand, is a backwards-compatible > community-maintained fork, which has most of those issues fixed and > will even support Python 3 soon. > > I think this change would involve (1) running the test suite with > Pillow, (2) updating the documentation and (3) updating the ImageField > warning shown when PIL is not installed. Looks like an easy change. > What do you think? Yes, we'll have to choose a Python 3-compatible replacement for PIL. I've converted your email into a ticket: https://code.djangoproject.com/ticket/19934 I assume that Pillow and PIL are API-compatible. Django could fallback to PIL if Pillow isn't installed, to preserve backwards compatibility. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
