While it can be a complex process at times, upgrading to the latest Django\nversion has several benefits:
\nDodano nowe funkcje i ulepszenia.
Bugi naprawione.
Older version of Django will eventually no longer receive security updates.\n(see Supported versions).
Upgrading as each new Django release is available makes future upgrades less\npainful by keeping your code base up to date.
Here are some things to consider to help make your upgrade process as smooth as\npossible.
\nIf it’s your first time doing an upgrade, it is useful to read the guide\non the different release processes.
\nAfterwards, you should familiarize yourself with the changes that were made in\nthe new Django version(s):
\nRead the release notes for each «final» release from\nthe one after your current Django version, up to and including the version to\nwhich you plan to upgrade.
Look at the deprecation timeline for the\nrelevant versions.
Pay particular attention to backwards incompatible changes to get a clear idea\nof what will be needed for a successful upgrade.
\nIf you’re upgrading through more than one feature version (e.g. 2.0 to 2.2),\nit’s usually easier to upgrade through each feature release incrementally\n(2.0 to 2.1 to 2.2) rather than to make all the changes for each feature\nrelease at once. For each feature release, use the latest patch release (e.g.\nfor 2.1, use 2.1.15).
\nThe same incremental upgrade approach is recommended when upgrading from one\nLTS to the next.
\nIn most cases it will be necessary to upgrade to the latest version of your\nDjango-related dependencies as well. If the Django version was recently\nreleased or if some of your dependencies are not well-maintained, some of your\ndependencies may not yet support the new Django version. In these cases you may\nhave to wait until new versions of your dependencies are released.
\nBefore upgrading, it’s a good idea to resolve any deprecation warnings raised\nby your project while using your current version of Django. Fixing these\nwarnings before upgrading ensures that you’re informed about areas of the code\nthat need altering.
\nIn Python, deprecation warnings are silenced by default. You must turn them on\nusing the -Wa Python command line option or the PYTHONWARNINGS\nenvironment variable. For example, to show warnings while running tests:
Linux / macOS
$ python -Wa manage.py test\nWindows
...\\> py -Wa manage.py test\nIf you’re not using the Django test runner, you may need to also ensure that\nany console output is not captured which would hide deprecation warnings. For\nexample, if you use pytest:
\n$ PYTHONWARNINGS=always pytest tests --capture=no\nResolve any deprecation warnings with your current version of Django before\ncontinuing the upgrade process.
\nThird party applications might use deprecated APIs in order to support multiple\nversions of Django, so deprecation warnings in packages you’ve installed don’t\nnecessarily indicate a problem. If a package doesn’t support the latest version\nof Django, consider raising an issue or sending a pull request for it.
\nOnce you’re ready, it is time to install the new Django version. If you are using a virtual environment and it\nis a major upgrade, you might want to set up a new environment with all the\ndependencies first.
Jeśli zainstalowałeś Django z pip, możesz użyć flagi --upgrade lub -U:
Linux / macOS
$ python -m pip install -U Django\nWindows
...\\> py -m pip install -U Django\nWhen the new environment is set up, run the full test suite for your application. Again, it’s useful to turn\non deprecation warnings on so they’re shown in the test output (you can also\nuse the flag if you test your app manually using manage.py runserver):
Linux / macOS
$ python -Wa manage.py test\nWindows
...\\> py -Wa manage.py test\nAfter you have run the tests, fix any failures. While you have the release\nnotes fresh in your mind, it may also be a good time to take advantage of new\nfeatures in Django by refactoring your code to eliminate any deprecation\nwarnings.
\nJeśli jesteś dostatecznie pewny, że Twoja aplikacja działa z nową wersją Django, to możesz przejść dalej i wdrożyć swój ulepszony projekt Django.
\nIf you are using caching provided by Django, you should consider clearing your\ncache after upgrading. Otherwise you may run into problems, for example, if you\nare caching pickled objects as these objects are not guaranteed to be\npickle-compatible across Django versions. A past instance of incompatibility\nwas caching pickled HttpResponse objects, either\ndirectly or indirectly via the cache_page()\ndecorator.