I fully understand the convenience of being able to read just the header. (it's ok if it doesn't go in the sources) I'm wondering, could it be possible to adapt the loop to read bigger chunks maybe.
Nevertheless, in my case, the 35 meg is a TIFF file, while a 10 meg file that is also very slow is a standard PNG file. Fredz./ On Fri, Jul 17, 2009 at 6:39 PM, Sam Tregar <[email protected]> wrote: > On Fri, Jul 17, 2009 at 4:27 PM, Javier Guerra <[email protected]> wrote: > >> >> On Fri, Jul 17, 2009 at 8:10 PM, Fredz./<[email protected]> >> wrote: >> > I might be loading the image in memory, but it sure seems 1000x faster >> > when you reach images the size of 10 megs and more. >> >> this assumes that it would have to read the whole file anyway. some >> formats have the size info in a header on the first few KBs. i >> believe on those cases PIL can give the info as soon as possible. >> > > Which does invite the question - what format is this monster 35MB image > in? Maybe if you choose a smarter format the size info will be in the > header! > > -sam > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
