[OE-core] [PATCH 28/45] swig: move to Python 3

[Alexander Kanavin]

On 05/27/2016 04:21 PM, Mike Looijmans wrote:

> This probably means that projects using Python 2 extensively will be
> forced to either "freeze" the OE version to the state before the
> transition or attempt to maintain a "python-2" fork.

Not at all. Oe-core will continue to provide python 2 recipes, swig is 
now compatible with both 2 and 3, the supporting 3rd party py2 libraries 
that will be removed from oe-core will be added to meta-oe at the same 
time (python-dbus), or should be trivial to add, if anyone actually 
needs them (python-git). Python 2 users should be able to continue with 
minimal (or zero) tweaks.

That said, we want to make it clear that it's time to get serious about 
moving to Python 3. It's been out for many years, the only excuses left 
are the bad ones.

Alex