#16675: Refactor the class/function loading code to use common API
-------------------------------------+-------------------------------------
Reporter: jezdez | Owner: nobody
Type: | Status: new
Cleanup/optimization | Component:
Milestone: | Uncategorized
Version: 1.3 | Severity: Normal
Keywords: | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
There are countless code snippets in Django that load a particular
callback or backend and each handle the possible exceptions differently.
I think for the most of those examples we can use a common API which would
lower the chance of breakage as well be useful to users.
Jonas Obrist implemented this kind of thing in his django-load app
(http://readthedocs.org/docs/django-load/en/latest/).
--
Ticket URL: <https://code.djangoproject.com/ticket/16675>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
