#18717: Setting attributes on deferred objects should trigger field's
descriptor's
__set__()
-------------------------------------+-------------------------------------
Reporter: Kronuz | Owner: shaz
Type: Bug | Status: assigned
Component: Database layer | Version: 1.4
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by timgraham:
Old description:
> Setting attributes on deferred objects (DeferredAttribute) should trigger
> original field's descriptor's __set__() (if any).
> Currently, specially for custom fields set up as descriptors defining
> __set__(), the original field's __set__ is never called when setting
> object attributes on deferred fields.
New description:
Setting attributes on deferred objects (`DeferredAttribute`) should
trigger original field's descriptor's `__set__()` (if any).
Currently, specially for custom fields set up as descriptors defining
`__set__()`, the original field's `__set__` is never called when setting
object attributes on deferred fields.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/18717#comment:4>
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/064.fc8da0fae617881c4679864991bb768e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
