#30252: ImageField's to_python() stores reference to closed Image object
-------------------------------------+-------------------------------------
Reporter: Felix Dreissig | Owner: nobody
Type: Bug | Status: new
Component: File | Version: 2.1
uploads/storage |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Felix Dreissig):
Thanks for your quick response.
I could probably come up with a test case, but it will take some time. How
would you like it? As a GitHub pull request (which would introduce a
failing test until a fix is commited), or as a patch in this ticket?
A fix I could think of would be re-`open()` ing the Image after
verification and storing that object to the `image` attribute. Or removing
the attribute completely (since it appears useless in its current state),
but that would break an (undocumented) API.
--
Ticket URL: <https://code.djangoproject.com/ticket/30252#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.78dbe4407fbf116602e8f872f53b20ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
