| Summary: | python 3.6/3.7 upgrade | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexander Kanavin <alex.kanavin> |
| Component: | devtools / tool chain | Assignee: | 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
As this has been deferred to 2.6, we should consider going straight to python 3.7 in that release cycle. *** Bug 12901 has been marked as a duplicate of this bug. *** What is the current status of Python 3.6 / 3.7 support? patches are proposed on ml. it will mostly be considered for 2.7 release On which mailing list may I find those patches? Does anyone happen to have a link? 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/ @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? Its in the poky layer where the python3 recipe resides: https://github.com/kraj/poky/commit/e349b239c8833bcdad9b1ff1a0702ace2db71959 in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-devtools/python/python3_3.7.2.bb?id=e2c3247c233876ab090c9ce3d5325a6d46ab350f please close if you aggree I agree :) |