while using PIL 1.16 recently, I noticed that ImageStat seems to do a
silent convert to mode L when given a mode F image. Looping though the
image manually using the im.load() access object gives me a different
maximum than ImageStat.Stat(im).extrema. Is this intentional? it
doesn't seem to be documented. Is it perhaps been fixed?
Edward
Unicorn School
_______________________________________________
Image-SIG maillist  -  Image-SIG@python.org
http://mail.python.org/mailman/listinfo/image-sig

Reply via email to