(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 --> <...") |
|||
| Line 91: | Line 91: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
You should be able to install two web-apps, one requiring python2-django and one requiring python3-django. (TODO: provide actual package names) | |||
# dnf install (package 1) | |||
# see python2-django is installed as dependency | |||
# run that package | |||
# dnf install (package 2) | |||
# verify python3-django is installed as dependency | |||
# package 1 still works | |||
# package 2 works as well | |||
# dnf remove package 1 | |||
# package 2 still works | |||
== User Experience == | == User Experience == | ||
Revision as of 13:45, 6 December 2017
Change Proposal Name Django-2.0
Summary
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.
Owner
- Name: Matthias Runge
- Email: <mrunge@matthias-runge.de>
- 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.
Scope
- 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.
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- 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
You should be able to install two web-apps, one requiring python2-django and one requiring python3-django. (TODO: provide actual package names)
- dnf install (package 1)
- see python2-django is installed as dependency
- run that package
- dnf install (package 2)
- verify python3-django is installed as dependency
- package 1 still works
- package 2 works as well
- dnf remove package 1
- 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)