Matthew Dapena-Tretter

> What do you think, should we manually list all available exceptions in that except block? > Definately this list includes MemoryError and IOError (cannot identify image file). Maybe smth...

Maybe we can spin that strategy off into another issue since this one already has two things. (Catching errors during generation and raising errors when image doesn't exist.)

@ninapavlich Sounds good to me. I'm not too crazy about the name "Safe" though…JIT is just as safe. Can we think of something less scary?

Yeah, that makes sense. You'll still have the overhead of guaranteeing the file's existence on access (but caching elimates that). Your use case is basically the reason that strategies exist....

That's odd! Can you share your admin class? Also, which version of Django are you using?

@fish2000 Very strange. I can't reproduce this. Can you share the admin class?

It's not likely to be your `MEDIA_ROOT` since your S3 storage class probably doesn't use that setting. Try using `heroku run bash` to open up a shell and then start...

What version of PILKit is installed?

What storage class are you using?

Is this happening with all the images or just one? Also, could you share the version of PIL/Pillow you're using? (Sorry a response has been so long in coming. I...