I created a ticket for this problem:
https://code.djangoproject.com/ticket/20187
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr
Hi Aymeric,
Thanks for your reply.
Actually I'm just using a memory cache for the response, so I'm not
pickling it.
My thoughts are:
1. The __iter__ method of a HttpResponse should create an instance of a
separate iterator class to iterate over the container. It should not return
sel
On 25 mars 2013, at 18:02, SteveB wrote:
> I suspect this is a bug. Any thoughts?
Yes, it's annoying, all the more since Django exposes response.content as an
attribute.
> This works, but makes my code dependent on the internals of the HttpResponse
> class, which isn't great. Any better ideas
With the change to HttpResponse made in Django 1.5, I'm finding that in my
code, which caches a generated response, results in an empty body when that
page is requested a second time. The first time the page is requested, it
is not in the cache, and the page is generated normally and added to th
