[OE-core] [PATCH 00/45] Move recipes to use Python 3 whenever possible

[alexander.kanavin at linux.intel.com]

>> Consequently, rpm's python bindings (required by smartpm) stay at python
>> 2 as well
>> for now, even tough python 3 seems to be supported.
>
> Is there a porting guide or similar that can used to help identify what
> types of
> changes are needed.  I am not at all familiar with what python 3 needs
> specifically, but I do expect we will need to port these items.

Of course, there's a ton of such guides on the net. Here's the official one:
https://docs.python.org/3/howto/pyporting.html

> The yum version of createrepo will not work.  We need to port forward the
> component as appropriate -- or modify smartpm to use a newer version --
> assuming
> we can add missing pieces, as necessary.  (key is smartpm and createrepo
> need to
> be kept in sync.)

Can you say why it won't work, specifically, if we also replace smartpm
with yum or dnf at the same time? The only alternative I see is that we
have to fork the old version of createrepo and the abandoned upstream of
smartpm, port them to Python 3, and maintain them going forward - not a
light undertaking.

> Please create one (or three) defects and assign them to me for smartpm,
> createrepo, and rpm python3 support.  (I doubt I'll be the one doing the
> work,
> but I'll do my best to find someone to do the work.)

Yes, I'll do that now.

>> 5) LSB spec is implicitly requiring Python 2 (via requirement for
>> '/usr/bin/python').
>
> I expect the LSB will require python 2 for a while.  So we will need to
> continue
> to ensure that python 2 works, as well as python3.

Of course, Python 2 will be supported by upstream at least until 2020, and
so it'll be provided by oe-core at least until then. 2.7.12 should appear
soon.

Alex