Looking over Simon's patch for signed cookies, I noticed that yet another feature needs to write its own "load a backend from a setting" function. A quick search of the codebase shows at least four other instances of this behavior (shown below), and it seems it's only going to get more common going forward. Is there a way we can factor some of this out into a utility? As it stands now, the author of each feature needs to figure out which one to copy from, which means figure out how they're different, even though many of those differences are just stylistic.
django.contrib.auth.load_backend() django.core.files.storage.get_storage_class() django.template.loader.find_template_loader() django.db.load_backend() Database loaders are a bit of an oddball, since they load an entire module's worth of classes based on the setting, but there's repetition even there. Unfortunately, I can't dedicate much of my own time at the moment to look into this, but I think it'd be worth doing before we start adding even more features with configurable backends in the future. -Marty -- 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.
