Following the advice of David Sanders and Mariusz Felisiak, I'm coming here with my proposal rather than continuing on with the ticket system (see ticket #34035 <https://code.djangoproject.com/ticket/34035>).
I understand the reluctance to make this change. However, things change with web browsers and I believe web frameworks should make changes to stay in line with the web browsers. It used to be less common for web browsers to consider EXIF orientation, but now it's the standard. ImageField being able to save the image dimensions to another field is very useful but for my use case it's broken because it doesn't consider EXIF orientation so there are cases where the dimensions are the opposite of what they should be. I highly doubt I'm alone in this. Maybe there should be a setting that can be passed into ImageField to avoid breaking existing projects. I definitely think this should be part of Django rather than having the developers need to add this logic to each of their Django projects that need it. Thoughts? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c51cfad1-df74-446a-a341-53a007a9ae9fn%40googlegroups.com.
