Changes/Python3.7

Python 3.7

Summary

Update the Python 3 stack in Fedora from Python 3.6 to Python 3.7.

Owner

• Name: Charalampos Stratakis
• Name: Miro Hrončok
• Name: Tomáš Orsava
• Name: Petr Viktorin

• Email: python-maint@redhat.com
• Release notes owner:

Current status

• Targeted release: Fedora 29
• Last updated: 2018-03-14
• Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Python 3.7 adds numerous features and optimizations. See the upstream notes at Features for 3.7 and What's new in 3.7.

Benefit to Fedora

Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Python 3. Packages in Fedora can use the new features from 3.7.

Scope

• Proposal owners:
  1. Retire python37 from F29+
  2. Update python3 to what was in python37
     • Mass rebuild all the packages that BR python3/python3-devel/... (~2300 listed in Python 3 Porting Database for Fedora)
  3. Reintroduce python36 from Fedora 25. Update it to have all fixes and enhancements from python3 in Fedora 28 (or 29 before this change)

• Other developers: Maintainers of packages that fail to rebuild during the mass rebuild will be asked, using bugzilla, to fix or remove their packages from the distribution. If any issues appear, they should be solvable either by communicating with upstreams first and/or applying downstream patches. Also the package maintainers should have a look at: Porting to Python 3.7. And python-maint team will be available to help with fixing issues.

• Release engineering: #Releng issue number TODO A targeted rebuild for all python packages will be required, before the mass rebuild.
  • List of deliverables: nope

• Policies and guidelines: nope

• Trademark approval: nope

Upgrade/compatibility impact

All the packages that depends on Python 3 must be rebuilt. User written Python 3 scripts/applications may require a small amount of porting, but mostly Python 3.6 is forward compatible with Python 3.7.

How To Test

N/A (not a System Wide Change)

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)