# Django 6.0.7 - dokumentacja

# Jak zaktualizować Django do nowszej wersji

Upgrading Django to the latest version offers several benefits:

- New features and improvements become available.

- Naprawione błędy.

- Older versions of Django eventually stop receiving security updates (see Supported versions).

- Upgrading with each new release helps keep your code base current and makes future upgrades smoother.

Tools to help with version upgrades

Django has a vibrant ecosystem. There are automated upgrade helpers highlighted on the Community Ecosystem page.

Here are some things to consider to help make your upgrade process as smooth as possible.

## Wymagane Czytanie

If it’s your first time doing an upgrade, it is useful to read the guide on the different release processes.

Afterward, you should familiarize yourself with the changes that were made in the new Django version(s):

- Read the release notes for each «final» release from the one after your current Django version, up to and including the version to which you plan to upgrade.

- Look at the deprecation timeline for the relevant versions.

Pay particular attention to backwards incompatible changes to get a clear idea of what will be needed for a successful upgrade.

If you’re upgrading through more than one feature version (e.g. 2.0 to 2.2), it’s usually easier to upgrade through each feature release incrementally (2.0 to 2.1 to 2.2) rather than to make all the changes for each feature release at once. For each feature release, use the latest patch release (e.g. for 2.1, use 2.1.15).

The same incremental upgrade approach is recommended when upgrading from one LTS to the next.

## Zależności

In most cases it will be necessary to upgrade to the latest version of your Django-related dependencies as well. If the Django version was recently released or if some of your dependencies are not well-maintained, some of your dependencies may not yet support the new Django version. In these cases you may have to wait until new versions of your dependencies are released.

## Radzenie sobie z ostrzeżeniami o deprecjacji

Before upgrading, it’s a good idea to resolve any deprecation warnings raised by your project while using your current version of Django. Fixing these warnings before upgrading ensures that you’re informed about areas of the code that need altering.

In Python, deprecation warnings are silenced by default. You must turn them on using the `-Wa` Python command line option or the `PYTHONWARNINGS` environment variable. For example, to show warnings while running tests:

/ 

    $ python -Wa manage.py test

    ...\> py -Wa manage.py test

If you’re not using the Django test runner, you may need to also ensure that any console output is not captured which would hide deprecation warnings. For example, if you use pytest:

    $ PYTHONWARNINGS=always pytest tests --capture=no

Rozwiąż wszelkie ostrzeżenia o deprecjacji z obecną wersją Django przed kontynuowaniem procesu aktualizacji.

Third party applications might use deprecated APIs in order to support multiple versions of Django, so deprecation warnings in packages you’ve installed don’t necessarily indicate a problem. If a package doesn’t support the latest version of Django, consider raising an issue or sending a pull request for it.

## Instalacja

Once you’re ready, it is time to install the new Django version. If you are using a `virtual environment` and it is a major upgrade, you might want to set up a new environment with all the dependencies first.

Jeśli zainstalowałeś Django z pip, możesz użyć flagi `--upgrade` lub `-U`:

/ 

    $ python -m pip install -U Django

    ...\> py -m pip install -U Django

## Testowanie

When the new environment is set up, run the full test suite for your application. Again, it’s useful to turn on deprecation warnings on so they’re shown in the test output (you can also use the flag if you test your app manually using `manage.py runserver`):

/ 

    $ python -Wa manage.py test

    ...\> py -Wa manage.py test

After you have run the tests, fix any failures. While you have the release notes fresh in your mind, it may also be a good time to take advantage of new features in Django by refactoring your code to eliminate any deprecation warnings.

If you are upgrading to an alpha, beta, or release candidate, please see our guide on How to test pre-release versions of Django for more specific tips about catching regressions and reporting bugs.

## Wdrażanie

Jeś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.

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 `HttpResponse` objects, either directly or indirectly via the `cache_page()` decorator.