#25069: Make _unregister_lookup be public API
-------------------------------------+-------------------------------------
Reporter: coldmind | Owner: coldmind
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
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 charettes):
My point is that I'd rather have a method (private or public) that deals
with the implementation details of lookup unregistration than moving this
logic in the tests by directly assigning to `class_looukps`.
--
Ticket URL: <https://code.djangoproject.com/ticket/25069#comment:5>
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/066.f00c670f97f576523cf06db1d730db73%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
