From Fedora Project Wiki
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
For details on how to fill out this form, see the documentation.

Change Proposal Name Django 4.0


Update Django to version 4.0.


Current status

  • Targeted release: Fedora Linux 36
  • Last updated: 2022-01-05
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The Django project has regular releases about every 9 months. Django 4.0 is a major milestone, and this Change will bring the Fedora included version to the latest version.

The immediate step is to bump the python-django package to version 4.0. It is expected, that dependent packages will be updated as well, or retired, if they haven't seen an update for long time.


Benefit to Fedora

This updates to the latest Django version and allows to use the distribution provided version to be used both in new developments and also with latest Django applications.

The upstream project has more info on what's new

The risk of not completing this change is that the next update will be more disruptive, Django 4.1 is planned for about the same time as Fedora 37 will land.


  • Proposal owners: python-django will be updated to version 4.0.
  • Other developers:

Other developers or maintainers will have to test their packages with Django 4.0.

  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

How To Test

The python3-django package has to be installed in order to run the test.

   django-admin --version


Django (the fedora package name is python-django) has a few dependent packages which should get updated (or removed) as noted above. If they were not updated for Django 4.0, that probably means that their upstream is not very active anymore.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Extensive upstream documentation can be found at

N/A (not a System Wide Change)

Release Notes