On Mon, Dec 21, 2009 at 10:39 PM, Jeremy Dunck <jdu...@gmail.com> wrote: > On Mon, Dec 21, 2009 at 8:22 AM, Marty Alchin <gulop...@gmail.com> wrote: > ... >> django.contrib.auth.load_backend() >> django.core.files.storage.get_storage_class() >> django.template.loader.find_template_loader() >> django.db.load_backend() > > Also, django.core.cache.get_cache
Also django.core.email, django.contrib.messages, django.contrib.sessions... the list goes on. The difficulty is that they aren't all exactly the same: * The email backend loader take arguments that configure the underlying mail connection * The cache backend needs to handle a URI-style definition. * The template loaders need to have fallback support for old-style template loaders, as well as handling checks for whether the loader is available in the current environment. Similar eccentricities exist in many of the backends. In short - yes, factoring this out into a common utility is desirable. However, it's a lot easier said than done. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
