#20493: Add a warning that objects may not be picklable across Django versions
-------------------------------+------------------------------------
Reporter: cataliniacob | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by cataliniacob):
I would make the suggestion a bit stronger, something like:
... you should consider clearing your cache after upgrading. Otherwise you
may run into problems ...
I don't know if people clearly make the connection between "I'm using
@cache_page" and "I'm caching pickled HttpResponse objects", so I see the
stronger suggestion as a hint that you shouldn't just dismiss the next
section (doesn't apply to me, I'm not pickling anything, I'm just using
@cache_page).
But in general it sounds fine to me!
--
Ticket URL: <https://code.djangoproject.com/ticket/20493#comment:4>
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.3cc112cb033a2b08d734b937983ef59a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
