#31475: Recursion issue when deleting related objects
-------------------------------------+-------------------------------------
Reporter: Matt Drew | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Simon Charette):
Given we've had two reports due to `__init__` overrides so far we might
want to consider disabling the optimization introduced in
f110de5c04818b8f915dcf65da37a50c1424c6e6 when `model_cls.__init__ is not
Model.__init__` or `post_init` receivers are attached.
I'm kind of torn here though because accessing field unconditionally
during model initialization will break down the road somewhere else but
learning about this misuse through a recursion error traceback is
definitely confusing. Thoughts?
--
Ticket URL: <https://code.djangoproject.com/ticket/31475#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.713a1ffa4c24773e6e1d60d4527fcb34%40djangoproject.com.
