On Sat, Nov 1, 2008 at 8:32 PM, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> On Nov 2, 2:52 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>> Assuming vary_on_get() with no parameters means no variance (other
>> than the HTTP Vary headers), then [...]
>
> That seems confusing - the decorator name
On Nov 2, 2:52 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> Assuming vary_on_get() with no parameters means no variance (other
> than the HTTP Vary headers), then [...]
That seems confusing - the decorator name seems to imply that it would
vary on any get attribute (even though this is the
On Nov 1, 1:38 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
>
> Really, there is not reluctance to get input on what should be fixed before
> 1.0.1 is released. It's just that input in the form of working patches with
> tests and doc is far more valuable than a simple bit on a ticket. The list
On Sat, Nov 1, 2008 at 9:45 AM, bo <[EMAIL PROTECTED]> wrote:
> One aid in this area would be to remove the dependancy of
> context_processor.auth in the Admin world (which most certainly needs
> the user, messages and perms in the context)
You can already do this - simply make your own subclass
I regards to
http://groups.google.com/group/django-developers/browse_thread/thread/2bad3ad84e9beb81
One aid in this area would be to remove the dependancy of
context_processor.auth in the Admin world (which most certainly needs
the user, messages and perms in the context)
Admin can detect if
This seems to be part of it. I'm not sure if there is a sort_by fix in
there or not. It would be nice to be able to pass some of these fields
to the add user form. It would look much more uniform.
On Oct 31, 6:00 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> This just seems like a
On Tue, Dec 6, 2005 at 9:37 AM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
...
> Looks like vary_on_get is the most popular choice. So here's how that
> might work:
>
> @vary_on_get('id')
> def my_view(request):
>id = request.GET.get('id', None)
To be clear, the generated cache key would
Picking up an old thread (because it is still relevant)
On 6 Dec 2005, 15:37, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> The remaining question is: What's the behavior if vary_on_get() isn't
> specified for a particular view? Do we cache everything (including
> separate cache entries for any
hi
i saw that a django tarball is now in pypi but the version ident is
"1.0.1 beta 1".
i am not completly shur if i am right, but the spaces in the version
makes it impossible to use this version directly to download from pypi
via setuptools, buildout etc.
it would be nice to include django as
Hi!
Currently query parameters are ignored when using the cache decorator
for views (only the path segment [3] is used to determine the key).
This impacts performance for Django sites where query parameters are
used for filtering and sorting of lists of items (a common use case).
I found an old
10 matches
Mail list logo
