From Fedora Project Wiki

< Changes

Revision as of 13:21, 12 December 2017 by Churchyard (talk | contribs) (Summary update, add myself to owners)


Django 2.0

Summary

This change is about upgrading Package-x-generic-16.pngpython-django to version 2.0. The latest Django release drops support for Python 2, but a few Django apps packaged in Fedora do not yet support Python 3.

Owner

Current status

  • Targeted release: Fedora 28
  • Last updated: 2017-12-12
  • 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.


Scope

  • Proposal owners: drop Python2 subpackage from python-django, upgrade python-django to Django-2.0 and package Django-1.11.x for Python2 only.
  • 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:
    • Python packaging guidelines
    • Documentation should be provided
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

You should be able to install two web-apps, one requiring python2-django and one requiring python3-django. (TODO: provide actual package names)

  1. dnf install (package 1)
  2. see python2-django is installed as dependency
  3. run that package
  4. dnf install (package 2)
  5. verify python3-django is installed as dependency
  6. package 1 still works
  7. package 2 works as well
  8. dnf remove package 1
  9. package 2 still works

User Experience

N/A (not a System Wide Change)

Dependencies

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

Documentation

N/A (not a System Wide Change)

Release Notes