On 03/16/2018 07:06 AM, Tim Orling wrote:
I looked into 3.6 as well, but the sheer number of patches we apply is a
pain point to rebase.
I am inclined to vote for 3.6 first and pick up 3.7 when it matures a
bit and is more widely supported. I have fears of rather massive
failures in our python ecosystem (especially in meta-python). Perhaps
backward compatibility will be there, but I need to be convinced. If 3.7
is widely the _default_ in traditional distros we support, then I will
sing a different tune. Also, I hope to have a ptest strategy for python
by the end of 2.6, which would dramatically increase my comfort level.
Perhaps we can provide both and default to 3.6? Eventually we will have
to transition to 3.7, and I think it might be easier if it's widely
available in oe-core, even if it has known (or unknown) issues and is
off by default. We can then periodically test 3.7 on the AB etc, to
assess where things are.
Alex
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
