test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #20493 -- Added a warning that objects may not be picklable across Django versions 

Thanks cataliniacob for the suggestion and review.
This commit is contained in:
Tim Graham 2013-07-08 09:57:50 -04:00
parent da79ccca1d
commit 1084575163
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/howto/upgrade-version.txt
View File

@ -89,3 +89,11 @@ Deployment
When you are sufficiently confident your app works with the new version of 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>` Django, you're ready to go ahead and :doc:`deploy </howto/deployment/index>`
your upgraded Django project. 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.