On Mon, Dec 21, 2009 at 10:46 AM, Simon Willison
wrote:
> On Dec 21, 2:22 pm, Marty Alchin wrote:
>> 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.
>
> Yup - and as I copied and pasted it fro
On Dec 21, 2:22 pm, Marty Alchin wrote:
> 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.
Yup - and as I copied and pasted it from somewhere else I thought
exactly the same thing. Is this kind o
On Mon, Dec 21, 2009 at 10:39 PM, Jeremy Dunck wrote:
> On Mon, Dec 21, 2009 at 8:22 AM, Marty Alchin 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.c
On Mon, Dec 21, 2009 at 8:22 AM, Marty Alchin 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
--
You received this message because you are
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
