Bug 12375

Summary: python 3.6/3.7 upgrade
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Alexander Kanavin <alex.kanavin>
Component: devtools / tool chainAssignee: Derek Straka <derek>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: akuster, alejandr, alejandro.hernandez, meta.mr.watcher, meta.watcher, raj.khem, randy.macleod, richard.purdie, robin.l.jordan, t, wobupuyi, ypbzml
Version: 2.5   
Target Milestone: 4.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Alexander Kanavin 2017-11-22 15:02:43 UTC
Upgrading Python to 3.6 has already been missed twice, so I believe it should really be completed in this release cycle. Python 3.7 comes out in June 2018 [1], and if we do nothing now, it will be even harder to update.

[1] https://www.python.org/dev/peps/pep-0537/
Comment 1 Alexander Kanavin 2018-03-01 20:28:06 UTC
As this has been deferred to 2.6, we should consider going straight to python 3.7 in that release cycle.
Comment 2 Alexander Kanavin 2018-08-31 16:57:10 UTC
*** Bug 12901 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Kuhn 2018-10-31 08:37:51 UTC
What is the current status of Python 3.6 / 3.7 support?
Comment 4 Khem Raj 2018-10-31 13:32:36 UTC
patches are proposed on ml. it will mostly be considered for 2.7 release
Comment 5 Tristan Ramseyer 2018-11-11 22:15:20 UTC
On which mailing list may I find those patches? Does anyone happen to have a link?
Comment 6 Randy MacLeod 2018-11-12 00:00:00 UTC
The openembedded-core email list:
   http://lists.openembedded.org/pipermail/openembedded-core/2018-November/275727.html
see:
   https://www.openembedded.org/wiki/Mailing_lists

You can also use patchworks. I think this is the most recent python upgrade:
   https://patchwork.openembedded.org/series/14778/
Comment 7 Joseph L. Benton 2018-11-14 20:23:16 UTC
@Randy MacLeod, the path is talking about "Rebased until e349b239c8833bcdad9b1ff1a0702ace2db71959" but this commit does not exist in openembedded-core.

Any idea what commit the path is based on?
Comment 8 Tristan Ramseyer 2018-11-14 20:28:59 UTC
Its in the poky layer where the python3 recipe resides: https://github.com/kraj/poky/commit/e349b239c8833bcdad9b1ff1a0702ace2db71959
Comment 10 Alexander Kanavin 2019-03-05 17:33:12 UTC
I agree :)