Re: Why not remove csrfmiddlewaretoken in CsrfViewMiddleware from request.POST?

On Thu, Aug 26, 2010 at 12:55 AM, mucisland wrote: > I posted this also in Django users but got no response - maybe the > question is too stupid or it was the wrong group... > > Here's the deal: > > I have various views which break on the additional

Re: MySQL index hints

On Thu, Aug 26, 2010 at 12:09 AM, Michael Manfre wrote: > > On Aug 24, 9:30 pm, Russell Keith-Magee > wrote: >> I don't follow your logic here. > > I guess I'm more of the mindset of query hints having as much to do > with the stored data as the schema

Re: django.contrib.views.login errors

I think, much less such emails will appear if this group will be renamed. **contributors* for example...* * * 2010/8/25 Karen Tracey > Please ask questions about using Django on django-users, not here. The > topic of this list is discussion of the development of Django

Why not remove csrfmiddlewaretoken in CsrfViewMiddleware from request.POST?

I posted this also in Django users but got no response - maybe the question is too stupid or it was the wrong group... Here's the deal: I have various views which break on the additional csrfmiddlewaretoken in request.POST when using the recommendet CSRF protection with CsrfViewMiddleware and {%

Re: MySQL index hints

On Aug 24, 9:30 pm, Russell Keith-Magee wrote: > I don't follow your logic here. I guess I'm more of the mindset of query hints having as much to do with the stored data as the schema and most hints would probably be a premature optimization or specific to a failing

Re: django.contrib.views.login errors

Please ask questions about using Django on django-users, not here. The topic of this list is discussion of the development of Django itself. Thanks, Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Feature question - caching

Again, sorry. In this case, I may in fact be proposing a change as I see that a feature applied according to docs doesn't work. jdunck wrote: > > On Wed, Aug 25, 2010 at 6:16 AM, buddhasystem wrote: >> >> Does Django native caching only work when a template is rendered? If

Re: Feature question - caching

OK, thanks. I'm still new here, apologies. Jirka Vejrazka wrote: > > Hi, > > you've just been asked on django-users to provide the code for your > view. Instead of that, you're cross-posting to django-developers that > is intended for development of Django itself. > > Please don't

Re: Feature question - caching

Hi, you've just been asked on django-users to provide the code for your view. Instead of that, you're cross-posting to django-developers that is intended for development of Django itself. Please don't cross-post and send your view code (including the caching parts) to django-users. Cheers

Re: Feature question - caching

On Wed, Aug 25, 2010 at 6:16 AM, buddhasystem wrote: > > Does Django native caching only work when a template is rendered? If I have a > view that just serves data wrapped in HttpResponse -- will it cache? In my > experience, it won't -- why?  Thanks so much. You've mailed the

Feature question - caching

Does Django native caching only work when a template is rendered? If I have a view that just serves data wrapped in HttpResponse -- will it cache? In my experience, it won't -- why? Thanks so much. -- View this message in context:

Re: Feature request - extend multiple templates

On 25 August 2010 08:59, Yo-Yo Ma wrote: > This is of course very painful, but the thing that makes it worse is > that I have to override each block 2 times with the exact same code > (foo_section/list.html and foo_section/form.html have the same tabs > and therefore

Feature request - extend multiple templates

Let's say I have a site with 5 sections, 6 main tabs per section, and 7 sub tabs per main tab. In order to display the correct tabs for a given view, I have to have: baseform.html baselist.html foo_section/form.html foo_section/list.html foo_section/spam_sub_section/form.html