Commit f551d5a3 authored by Tim Graham's avatar Tim Graham
Browse files

[1.5.x] Fixed #20493 -- Added a warning that objects may not be picklable across Django versions

Thanks cataliniacob for the suggestion and review.

Backport of 10845751 from master
parent abce5abe
Loading
Loading
Loading
Loading
+8 −0
Original line number Diff line number Diff line
@@ -89,3 +89,11 @@ Deployment
When you are sufficiently confident your app works with the new version of
Django, you're ready to go ahead and :doc:`deploy </howto/deployment/index>`
your upgraded Django project.

If you are using caching provided by Django, you should consider clearing your
cache after upgrading. Otherwise you may run into problems, for example, if you
are caching pickled objects as these objects are not guaranteed to be
pickle-compatible across Django versions. A past instance of incompatibility
was caching pickled :class:`~django.http.HttpResponse` objects, either
directly or indirectly via the :func:`~django.views.decorators.cache.cache_page`
decorator.