[SciPy-user] The IO library and image file formats -- compare with with PIL

[Robert Kern]

On Mon, Apr 21, 2008 at 12:13 PM, Stéfan van der Walt <stefan at sun.ac.za> wrote:
> On 21/04/2008, Zachary Pincus <zachary.pincus at yale.edu> wrote:
>
> >  Again, what I'm imagining wouldn't be a full-featured image IO
>  >  library, but something lightweight with no dependencies outside of
>  >  numpy, and potentially (if JPEG decoding isn't desired), no C-
>  >  extensions. (One could conceivably use numpy to do JPEG encoding and
>  >  decoding, but I've no interest in doing that...)
>
>  I love it -- let's do it (if everyone agrees, of course).  Having a
>  Python reference implementation is the way to go.  Should we separate
>  the io and the image processing routines, or put it all in
>  scipy.image?

If you are thinking about using PIL's code, I would prefer that it not
go into scipy. It smells too much like a fork, and I just don't want
scipy to get involved.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
 -- Umberto Eco