Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

[1.6.x] Fixed #20493 -- Added a warning that objects may not be pickl…

…able across Django versions

Thanks cataliniacob for the suggestion and review.

Backport of 1084575 from master
  • Loading branch information...
commit 67a6b5e53f62e90c7e8587d1f110aa3d7bb9afbf 1 parent cf8d093
@timgraham timgraham authored
Showing with 8 additions and 0 deletions.
  1. +8 −0 docs/howto/upgrade-version.txt
View
8 docs/howto/upgrade-version.txt
@@ -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.
Please sign in to comment.
Something went wrong with that request. Please try again.