From Fedora Project Wiki
(Mention fedpkg build --target=f29-python)
m (Notes from the upgrade link)
 
(3 intermediate revisions by the same user not shown)
Line 76: Line 76:
=== PEP 552 – Deterministic pycs ===
=== PEP 552 – Deterministic pycs ===


One change is notable from the packaging viewpoint: [https://www.python.org/dev/peps/pep-0552/ PEP 552] – “Deterministic pycs”. We may decide to use the new <code>UNCHECKED_HASH</code> mode, which would mean that bytecode cache is not validated on import, i.e. changing a RPM-installed <code>*.py</code> file manually will have no effect (unless the corresponding <code>__pycache__/*.pyc</code> is updated or removed).
One change is notable from the packaging viewpoint: [https://www.python.org/dev/peps/pep-0552/ PEP 552] – “Deterministic pycs”. We may decide to use the new <code>UNCHECKED_HASH</code> mode, which would mean that bytecode cache is not validated on import, i.e. changing a RPM-installed <code>*.py</code> file manually will have no effect (unless the corresponding <code>__pycache__/*.pyc</code> is updated or removed). '''We haven't decided for this.'''


=== Notes from the upgrade ===
There are notes from this upgrade available, so future upgrades may go smoother: [[SIGs/Python/UpgradingPython]]


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 91: Line 94:
* Proposal owners:
* Proposal owners:
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
*# Retire {{package|python37}} from F29+
*# Retire {{package|python37}} from F29+ (done)
*# Update  {{package|python3}} to what was in {{package|python37}}  
*# Update  {{package|python3}} to what was in {{package|python37}} (done)
*#* Mass rebuild all the packages that BR {{package|python3}}/{{package|python3-devel}}/... (~2300 listed in [http://fedora.portingdb.xyz/ Python 3 Porting Database for Fedora])  
*#* Mass rebuild all the packages that BR {{package|python3}}/{{package|python3-devel}}/... (~2300 listed in [http://fedora.portingdb.xyz/ Python 3 Porting Database for Fedora]) (built everything that was buildable)
*# Reintroduce {{package|python36}} from Fedora 25. Update it to have all fixes and enhancements from {{package|python3}} in Fedora 28 (or 29 before this change)
*# Reintroduce {{package|python36}} from Fedora 25. Update it to have all fixes and enhancements from {{package|python3}} in Fedora 28 (or 29 before this change) (package ready in git, will arrive on mass rebuild)


* Other developers: Maintainers of packages that fail to rebuild during the mass rebuild will be asked, using e-mail and bugzilla, to fix or remove their packages from the distribution. They should build their packages in the [https://koji.fedoraproject.org/koji/builds?order=-completion_time&tagID=4033&inherited=0&latest=1 f29-python side tag] via <code>fedpkg build  --target=f29-python</code>. 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: [https://docs.python.org/3.7/whatsnew/3.7.html#porting-to-python-3-7 Porting to Python 3.7]. And python-maint team will be available to help with fixing issues.
* Other developers: Maintainers of packages that fail to rebuild during the mass rebuild will be asked, using e-mail and 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: [https://docs.python.org/3.7/whatsnew/3.7.html#porting-to-python-3-7 Porting to Python 3.7]. And python-maint team will be available to help with fixing issues.
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


Latest revision as of 15:46, 9 July 2018


Python 3.7

Summary

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

Owner

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

Current status

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.

Important dates

  • 2018-06-11 Python 3.7.0 candidate 1
  • 2018-06-27 Python 3.7.0 final
  • 2018-07-11 Fedora 29 Mass Rebuild
  • 2018-08-14 Fedora 29 Change Checkpoint: Completion deadline (testable)

(From Python 3.7 Release Schedule and Fedora 29 Release Schedule.)

PEP 552 – Deterministic pycs

One change is notable from the packaging viewpoint: PEP 552 – “Deterministic pycs”. We may decide to use the new UNCHECKED_HASH mode, which would mean that bytecode cache is not validated on import, i.e. changing a RPM-installed *.py file manually will have no effect (unless the corresponding __pycache__/*.pyc is updated or removed). We haven't decided for this.

Notes from the upgrade

There are notes from this upgrade available, so future upgrades may go smoother: SIGs/Python/UpgradingPython

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

We will coordinate the work in a side tag and merge when ready.

  • Other developers: Maintainers of packages that fail to rebuild during the mass rebuild will be asked, using e-mail and 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.
  • Fedora QA: Based on some troubles with the change to 3.6, we'd like to have an ack from QA before we merge the side tag.
  • Release engineering: #7390 A targeted rebuild for all python packages will be required, before the mass rebuild.
  • Policies and guidelines: nope
  • Trademark approval: nope

Upgrade/compatibility impact

All the packages that depend 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 python37 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.

Dependencies

~2300 packages depends on python3. See scope section.

Contingency Plan

  • Contingency mechanism: Do not merge the side tag with rawhide. If the side tag has been merged and issues arise, that will justify a downgrade, then use an epoch tag to revert to 3.6 version (never needed before)
  • Contingency deadline: TBD
  • Blocks release? No
  • Blocks product? No

Documentation

Python 3.7 Release Schedule

Features for 3.7

What's new in 3.7

Porting to Python 3.7

Release Notes

  • Release Notes tracking: #133
Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Python3.7&oldid=522199"