From Fedora Project Wiki

< Changes

Revision as of 10:15, 14 March 2018 by Churchyard (talk | contribs) (User Experience)

Python 3.7


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


  • Email:
  • 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.


  • 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.
  • 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

Interested testers do not need special hardware. If you have a favorite Python 3 script, module, or application, please test it with Python 3.7 and verify that it still works as you expect. You can test it using Package-x-generic-16.pngpython37 even before this change is implemented, in Fedora 27 or 28.

Once the change is in place, test if you favorite Python apps are working as they were before. File bugzillas if they don't.

User Experience

Regular distro users shouldn't notice any change in system behavior other than the Python 3 interpreter will be in version 3.7.


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