Browse files

Fixed #20493 -- Added a warning that objects may not be picklable acr…

…oss Django versions

Thanks cataliniacob for the suggestion and review.
  • Loading branch information...
1 parent da79ccc commit 10845751632e843aeb21a030c7df7f9848bf65aa @timgraham timgraham committed Jul 8, 2013
Showing with 8 additions and 0 deletions.
  1. +8 −0 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`

0 comments on commit 1084575

Please sign in to comment.