#16675: Refactor the class/function loading code to use common API
-------------------------------------+-------------------------------------
Reporter: jezdez | Owner: nobody
Type: | Status: new
Cleanup/optimization | Component: Core (Other)
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* component: Uncategorized => Core (Other)
* stage: Unreviewed => Accepted
Comment:
I'll accept this in principle -- the "load a backend" pattern is something
that we've reimplemented far too many times. If we can pull this back to a
common API without losing all the edge cases, it seems like a no-brainer
to me.
From a first inspection, this snippet from Jonas looks like a good
approach to me -- I'd just need to see it in use for a couple of actual
use cases to be 100% convinced.
--
Ticket URL: <https://code.djangoproject.com/ticket/16675#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
