ImageWidget depends on having image decoder installed. about django-form-utils HOT 6 OPEN

Yes, this is not ideal. I'm not sure what would be a good way to reliably identify image values that wouldn't suffer from this problem; if you have a proposal (and better, a patch!) I'd welcome it.

from django-form-utils.

Hi,
Not quite sure I understand this. Why do we need to access the attribute when is not used?

if hasattr(value, 'width') and hasattr(value, 'height'):
    image_html = thumbnail(value.name, self.width, self.height)

from django-form-utils.

We access those attributes simply as a way of determining whether value is an image or not.

from django-form-utils.

I'm working with django-storages using S3. Apparently, the width/height will always be fetched and is described in this ticket: https://code.djangoproject.com/ticket/8307 . As a result, it has to read the file to get the up to date weight/height and will be slow for cloud based storages.

A similar issue on SO: http://stackoverflow.com/questions/5877497/storing-images-and-thumbnails-on-s3-in-django

Since I'm working on the ImageField, should I override this on my own widget to prevent the extra hit on S3?

from django-form-utils.

I don't know what you should do in that case, I haven't worked with ImageField and remote storages.

Regarding this specific bug, I'd welcome proposals of an alternative way to reliably tell whether value is an image that can be (potentially) thumbnailed.

from django-form-utils.

I can take a look next week, but if anyone else wants to take shot?

Sent from my iPhone 4S

On Apr 12, 2013, at 10:26 AM, Carl Meyer [email protected] wrote:

I don't know what you should do in that case, I haven't worked with
ImageField and remote storages.

Regarding this specific bug, I'd welcome proposals of an alternative way to
reliably tell whether value is an image that can be (potentially)
thumbnailed.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/2#issuecomment-16299210
.

from django-form-utils.