Imaging libraries in active development?

Prasad, Ramit ramit.prasad at jpmorgan.com
Fri Nov 30 00:04:40 CET 2012


Christian Heimes wrote:
> 
> Am 28.11.2012 19:14, schrieb Michael Torrie:
> > I'm curious.  What features do you need that pil doesn't have?  Other
> > than updating pil to fix bugs, support new image types or new versions
> > of Python, what kind of active development do you think it needs to
> > have? Maybe pil has all the features the original author wanted and is
> > pretty stable.  To judge a package on how fast it's changing seems a bit
> > odd to me.  Obviously you want to know that bugs can get fixed of
> > course.  Perhaps none have been reported recently.
> 
> PIL is missing a bunch of features like proper TIFF support (no
> multipage, g3/g4 compression and more), JPEG 2000, RAW and HDR image
> formats, tone mapping, proper ICC support, PEP 3128 buffer support ...
> 
> PIL is also rather slow. My smc.freeimage library can write JPEGs about
> six times faster, because it uses libjpeg-turbo. Only some Linux
> distributions have replaced libjpeg with the turbo implementation.
> 

Have you tried libtiff? I believe the author may read this list.
(He posted here for at least one release). 
http://code.google.com/p/pylibtiff/


Hope that helps,
Ramit


This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of
securities, accuracy and completeness of information, viruses,
confidentiality, legal privilege, and legal entity disclaimers,
available at http://www.jpmorgan.com/pages/disclosures/email.  



More information about the Python-list mailing list