From Fedora Project Wiki

< Changes

Revision as of 13:25, 6 December 2017 by Mrunge (talk | contribs) (Created page with " <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> <...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Change Proposal Name Django-2.0


This change is about upgrading python-django to version 2.0. The latest Django release drops support for Python 2, but still a few Django apps do not support Python 3.


  • Name: Matthias Runge
  • Email: <>
  • Release notes owner:

Current status

  • Targeted release: Fedora 28
  • Last updated: 2017-12-06
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The latest Django release 2.0 finally drops support for Python 2.7. Not all dependent applications can keep up with Djangos pace. This change describes a way how to enable both, keeping 2.7 compatibility and also leveraging the latest version.

Benefit to Fedora

Fedora will be able to provide both: latest and current release and also a fallback for applications, which do not support Python3 yet.


  • Proposal owners:
  • Other developers: Other developers, whose applications do work with Python3 and Django 2.0 will need to change the requirement to python3-django.
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)


N/A (not a System Wide Change)

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
  • Blocks product? product


N/A (not a System Wide Change)

Release Notes