Skip to content

Commit

Permalink
Fixed #20493 -- Added a warning that objects may not be picklable acr…
Browse files Browse the repository at this point in the history
…oss Django versions

Thanks cataliniacob for the suggestion and review.
  • Loading branch information
timgraham committed Jul 8, 2013
1 parent da79ccc commit 1084575
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions docs/howto/upgrade-version.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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.

0 comments on commit 1084575

Please sign in to comment.