Re: Python 3 for Bitbake

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2016-05-04 at 09:56 +0100, Richard Purdie wrote:
> My proposal is we decide to have the flag day, we queue up the 
> patches on a python3 branch both in oe-core and bitbake, then we 
> switch when we get successful autobuilder builds. I'd ideally like to 
> do this quite soon and get one with it (within a few weeks), leaving 
> plenty of time to handle issues and the other changes planned for 
> this release cycle and give other layers time to adapt.

To update, there are python3 branches in bitbake and OE-Core. With
those I've been able to "bitbake core-image-sato:do_rootfs core-image
-sato:do_populate_sdk" with the process and xmlrpc backends.

I've had a few issues to resolve, not least that we need to ensure
python is in utf-8 mode when it is started else files are opened as
ascii and all kinds of things break. Once started, you can't change the
default filesystem access mode and never will be able to for reasons
explained in a PEP.

I still haven't tried the various supporting tools, toaster, UIs other
than knotty, the oeqa framework.

I've separated out some patches and key fixes and submitted them, I
still have a monster patch which needs splitting up for both OE-Core
and bitbake though.

Help is welcome but a heads up on which area anyone is touching would
be appreciated. I know Ed plans to look at toaster.

Cheers,

Richard