From: "Burton, Ross" <ross.burton@intel.com>
To: Derek Straka <derek@asterius.io>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] splitting python's standard library
Date: Tue, 19 Dec 2017 13:43:50 +0000 [thread overview]
Message-ID: <CAJTo0LZ0e2iX84X_cOKxi9ziu9EgapG9_4MOKkPBEhKE=teCzg@mail.gmail.com> (raw)
In-Reply-To: <CADNbA1rNAafn+pUCuWJQ0AgrtwJpB4EUNfF7M1czOqVag7TL8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
On 19 December 2017 at 13:23, Derek Straka <derek@asterius.io> wrote:
> Cool. Works for me. Thanks.
>
There's an epic patch on the list which I'm reviewing right now that
drastically changes how the core Python library is packaged. If you'd like
to have a look, the almost-final (my bandaid fixes need to be squashed) is
at poky-contrib:ross/py.
Ross
[-- Attachment #2: Type: text/html, Size: 707 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Burton, Ross" <ross.burton@intel.com>
To: Derek Straka <derek@asterius.io>
Cc: Mark Asselstine <mark.asselstine@windriver.com>,
openembeded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: splitting python's standard library
Date: Tue, 19 Dec 2017 13:43:50 +0000 [thread overview]
Message-ID: <CAJTo0LZ0e2iX84X_cOKxi9ziu9EgapG9_4MOKkPBEhKE=teCzg@mail.gmail.com> (raw)
In-Reply-To: <CADNbA1rNAafn+pUCuWJQ0AgrtwJpB4EUNfF7M1czOqVag7TL8Q@mail.gmail.com>
On 19 December 2017 at 13:23, Derek Straka <derek@asterius.io> wrote:
> Cool. Works for me. Thanks.
>
There's an epic patch on the list which I'm reviewing right now that
drastically changes how the core Python library is packaged. If you'd like
to have a look, the almost-final (my bandaid fixes need to be squashed) is
at poky-contrib:ross/py.
Ross
next prev parent reply other threads:[~2017-12-19 13:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 19:00 [meta-python][PATCH] python-pyroute2: uprev to v0.4.21 (from 0.3.22) Mark Asselstine
2017-12-16 21:58 ` Derek Straka
2017-12-18 15:33 ` Mark Asselstine
2017-12-18 15:36 ` Christopher Larson
2017-12-18 16:15 ` Mark Asselstine
2017-12-18 16:37 ` [oe] " Alexander Kanavin
2017-12-18 16:37 ` Alexander Kanavin
2017-12-18 16:56 ` [oe] " Mark Asselstine
2017-12-18 16:56 ` Mark Asselstine
2017-12-18 20:17 ` [oe] " Derek Straka
2017-12-18 20:17 ` Derek Straka
2017-12-18 20:53 ` [oe] " Mark Asselstine
2017-12-18 20:53 ` Mark Asselstine
2017-12-18 21:02 ` S. Lockwood-Childs
2017-12-18 21:07 ` [oe] " Derek Straka
2017-12-18 21:07 ` Derek Straka
2017-12-18 21:26 ` [oe] " Mark Asselstine
2017-12-18 21:26 ` Mark Asselstine
2017-12-18 21:27 ` [oe] " Derek Straka
2017-12-18 21:27 ` Derek Straka
2017-12-19 7:56 ` splitting python's standard library Alexander Kanavin
2017-12-19 12:31 ` Derek Straka
2017-12-19 12:31 ` Derek Straka
2017-12-19 13:12 ` Alexander Kanavin
2017-12-19 13:12 ` Alexander Kanavin
2017-12-19 13:23 ` Derek Straka
2017-12-19 13:23 ` Derek Straka
2017-12-19 13:43 ` Burton, Ross [this message]
2017-12-19 13:43 ` Burton, Ross
2017-12-19 14:02 ` [oe] " Derek Straka
2017-12-19 14:02 ` Derek Straka
2017-12-28 22:29 ` [oe] " Derek Straka
2017-12-28 22:29 ` Derek Straka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJTo0LZ0e2iX84X_cOKxi9ziu9EgapG9_4MOKkPBEhKE=teCzg@mail.gmail.com' \
--to=ross.burton@intel.com \
--cc=derek@asterius.io \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.