#25687: Document how backends should monkey patch expressions
-------------------------------------+-------------------------------------
Reporter: jarshwah | Owner:
Type: | kristofclaes
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by carljm):
* stage: Ready for checkin => Accepted
Comment:
I don't think the code in the doc patch is quite right yet.
Also, I'm inclined to agree with @dedsm above -- what's the harm in
providing a public API that is effectively equivalent to doing this same
monkey-patching "under the hood"( ;-) ). Seems like there'd be no harm,
and it would give us more flexibility in the future if this does "become a
more common problem."
--
Ticket URL: <https://code.djangoproject.com/ticket/25687#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.680c5e7c847fa88b548d6274b2049dea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
