cache_page decorator previously used to have optional 'key_prefix'
argument, not only timeout. Is it gone? Can I use
@cache_page(3600, key_prefix='vasia')
def my_func(request)
...
Another question: in 'decorator_from_middleware_with_args' docstring
example stated:
Use like::
cache_page =
ssue and design decision is made
then OK :)
On 23 сен, 03:16, Luke Plant wrote:
> On Tuesday 22 September 2009 20:37:05 kmike wrote:
>
> > cache_page decorator previously used to have optional
> > 'key_prefix' argument, not only timeout. Is it gone? Can I use
>
>
If you search for `cache_page` decorator than it becomes clear that
traditional approach is to use it in now unsupported way:
myview = cache_page(myviewt, timeout)
For example here:
http://www.google.com/codesearch?hl=ru&sa=N&q=%22+%3D+cache_page%22++lang:python&ct=rr&cs_r=lang:python
nobody u
Some features from wiki proposal page don't get their way to google
spreadsheet (ex: 2 cache-related proposals) and they are not mentioned
in the final features page neither in a list of accepted features nor
in a list of rejected features. I understand that there are some valid
reasons for that b
Totally agree, bulk delete shouldn't be enabled by default.
One more issue with that: it is nice to be able to define actions
order in drop-down list. It can be achieved with very simple patch,
see http://code.djangoproject.com/ticket/10734 . But if we have delete
action (or any other action) ena
It's a very good opinion. I don't want any actions from parent model
admin class too.
Maybe it is worth opening a dedicated ticket?
On 5 апр, 05:56, Alex Gaynor wrote:
> On Sat, Apr 4, 2009 at 7:10 PM, kmike wrote:
>
> > Totally agree, bulk delete shouldn't be en
