#20493: HttpResponse objects cached with cache_page don't unpickle across Django
version leading to strange errors
-------------------------------+------------------------------------
Reporter: cataliniacob | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by carljm):
* component: Core (Cache system) => Documentation
* stage: Unreviewed => Accepted
Comment:
I think you're right that a requirement of cross-version unpicklability is
more than we want to commit to. We do have an "upgrading Django" page in
the docs now (https://docs.djangoproject.com/en/1.5/howto/upgrade-
version/); seems like it would make a lot of sense to add this as a note
there.
On a more long-term note, it might be worth considering whether the
caching middleware should cache a very simple "body, headers" data
structure instead of a full pickled `HttpResponse`. This would probably
break all kinds of code, though, since it means anything else tacked on to
the `HttpResponse` (and perhaps used by middlewares further down the
chain) would be missing.
--
Ticket URL: <https://code.djangoproject.com/ticket/20493#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.d7e2f0c207f8ba6be8ed7318e00263cd%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
