ANN: PIL 1.1.6 final (december 3, 2006)

> Steve Lianoglou wrote:
>
>> I just d/led the 1.1.6 and realized that it still
defaults to JPEG
>> instead of PNG and was wondering if this was an
oversight or not (I'm
>> changing mine back to PNG, though .
>
> it's a damned-if-change-it-damned-if-you-don't issue
,
and was too
> late for 1.1.6 anyway.  hopefully, 1.2 will provide
more flexible  
> image
> display facilities.

Completely understandable ...

Just out of curiosity, and so I know what to keep my eyes
open for  
since I changed it to PNG in my compile, what puts it in the
"damned - 
if-you-do" scenario? Is there something I should expect
to get hosed?

Thanks,
-steve

_______________________________________________
Image-SIG maillist  -  Image-SIGpython.org
htt
p://mail.python.org/mailman/listinfo/image-sig

Steve Lianoglou wrote:

> Just out of curiosity, and so I know what to keep my
eyes open for  
> since I changed it to PNG in my compile, what puts it
in the "damned - 
> if-you-do" scenario? Is there something I should
expect to get hosed?

performance, mostly.  doing lossless compression is a lot
more costly 
than doing lossy compression, or not doing compression at
all.

</F>

_______________________________________________
Image-SIG maillist  -  Image-SIGpython.org
htt
p://mail.python.org/mailman/listinfo/image-sig