#16326: Un-pickled TemplateResponse objects can't be re-pickled
------------------------------------+---------------------------------
Reporter: natrius | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Template system
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 1
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------+---------------------------------
Changes (by aaugustin):
* has_patch: 0 => 1
* needs_tests: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Since `TemplateResponse` contains code to deal with pickling, it's
reasonable to expect pickling - unpickling - pickling to work.
I think the rationale for stripping these attributes is to avoid storing a
large amount of computed data. I'd expect them to be regenerated during
unpickling, or on demand when the response is rendered; I haven't checked
the details.
--
Ticket URL: <https://code.djangoproject.com/ticket/16326#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
