[OE-core] [PATCHv2] python3: update to version 3.5.5 to fix security issues

[Tim Orling]

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.

—Tim
On Thu, Mar 15, 2018 at 10:17 AM Derek Straka <derek at asterius.io> wrote:

> I'm about half through the 3.6 updates.  I was hoping to get time in the
> next two weeks to finish it up.  I can just look at going to 3.7 if that's
> preferred.  I don't have a personal preference at this point.
>
> On Thu, Mar 15, 2018 at 1:06 PM, Alexander Kanavin <
> alexander.kanavin at linux.intel.com> wrote:
>
>> On 03/15/2018 06:37 PM, Derek Straka wrote:
>>
>>> Definitely.  I just didn't do the git add.  I'll send out the v2
>>> shortly.  Thanks for catching that!
>>>
>>
>> While we're on the subject of python upgrades, I'd like to ask, what kind
>> of plan do you have for 3.6/3.7? Is anything in progress? When you have
>> some kind of patch ready, we can test it on the autobuilder to iron out the
>> issues, and have it ready for when oe-core master reopens for version
>> updates.
>>
>> (I also think that at this point it makes sense to go straight to 3.7 and
>> test with various pre-release versions)
>>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180316/283ec8ae/attachment-0002.html>