We currently build two python runtimes, let's not. We should remove python2 from the default images, ensure there aren't any native packages with python-native DEPENDS, ensure all python2 using recipes have python3 support and (if possible) move all python2 recipes out of OE-Core.
I suspect we'll need it as a host tool for some time for the odd Python script used in recipes, but I'd like to think that we can stop building python2(-native).
This year it's not realistic. We can continue to reduce runtime py2 dependencies, and there'll be only a few holdouts, but py2 will be required at build time for quite some time still (and py2-native will be eliminated sooner than host py2). I'll post a 'round 2' py2 reduction patchset sometime next week, and I guess it becomes a once-a-year activity :)
Patchset posted for review: http://lists.openembedded.org/pipermail/openembedded-core/2017-April/136138.html From the cover letter, this is the sitation now: There are still a few py2 holdouts: - python-numpy (needed by a few recipes in meta-oe, shares code with python3-numpy) - python-nose (dependency of python-numpy) - python-scons (work to port it to py3 is ongoing now) - python-setuptools (dependency of python-scons) - bmap-tools - ltp - perf - asciidoc And a couple of packagegroups list python 2 as well: - packagegroup-self-hosted - packagegroup-core-lsb Let's revisit the situation with the above in a year or so.