From 10845751632e843aeb21a030c7df7f9848bf65aa Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 8 Jul 2013 09:57:50 -0400 Subject: [PATCH] Fixed #20493 -- Added a warning that objects may not be picklable across Django versions Thanks cataliniacob for the suggestion and review. --- docs/howto/upgrade-version.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/howto/upgrade-version.txt b/docs/howto/upgrade-version.txt index 8777f433f9b..fd018d4342f 100644 --- a/docs/howto/upgrade-version.txt +++ b/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 ` 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.