This change is about upgrading
to version 3.0. A compatibility package is not planned (but it is part of the contingency plan).
- Name: Miro Hrončok
- Email: <email@example.com>
- Name: Matthias Runge
- Email: <firstname.lastname@example.org>
- Targeted release: Fedora 32
- Last updated: 2019-09-18
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Django 3.0 begins the journey to making Django fully async-capable by providing support for running as an ASGI application.
This is in addition to the existing WSGI support. Django intends to support both for the foreseeable future. Async features will only be available to applications that run under ASGI, however.
Benefit to Fedora
Fedora will be able to provide the latest and current release of Django.
- Proposal owners: upgrade
to 3.0 prerelease as soon as this change is accepted (pull request).
- Django libraries/apps owners: Test that your packages work with Django 3. Update, contact upstream for help. Retire leaf packages with libraries if not compatible.
- Release engineering: no impact with Release Engineering is anticipated
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Eventually removed packages need to be obsoleted.
How To Test
- dnf update python3-django
Test that Fedora packaged Django applications still function as before, open Bugzillas if they don't.
Users using RPM installed Django to develop Django apps might be affected by this change. We shall recommend either using Python venvs for users who develop Django apps. See the developer portal, we are already recommending that.
- Contingency mechanism: (What to do? Who will do it?) Proposal owners will introduce a
python-django2compatibility package if everything goes south.
- Contingency deadline: beta freeze
- Blocks release? No
- Blocks product? No