[OE-core] [PATCH] Replace Python 3.3.x with Python 3.4.2

Burton, Ross ross.burton at intel.com
Thu Nov 13 22:52:12 UTC 2014


On 13 November 2014 20:23, Artur Wroblewski <wrobell at pld-linux.org> wrote:

> > Personally I'd prefer to see a working Python 3.4 integrated in one go
> > instead of having a broken 3.4 integrated for an unknown about of time.
> > Hopefully anyone else who is interested in 3.4 can step up and work on
> the
> > outstanding issues now that this patch is public (which is another good
> > reason to have a public repo with this in).
>
> If you specify some exit criteria for this, then I can try to improve
> the patch. But
> please keep in mind that Python 3.3 in Yocto is broken to such extent that
> it
> crashes due to missing essential modules.


 The exit criteria would be a patch to upgrade to 3.4 that doesn't come
with the caveat that seven of the patches need to be updated.  3.3 being
broken is a separate issue to upgrading to 3.4 and we should probably fix
3.3 first, backport that fix to dizzy, and then upgrade to 3.4.

I've filed a bug about the startup problem with just python3 installed
(#6967). Note that whilst this is a bug it's not fundamentally broken as
installing just python3-core (which python3 is an alias for - more on that
in a minute) won't pull in the bulk of the runtime library.  Installing
python3-core and python3-modules brings in the entire runtime, and the
interpreter starts up fine.

You could argue that whilst splitting out the core library is reasonable so
that minimal installs are possible, having "python3" not be the full Python
experience isn't reasonable.  I'd be inclined to agree here, and think that
python3 should be a meta-package that depends on all of Python.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20141113/92934cb7/attachment-0002.html>


More information about the Openembedded-core mailing list