From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] Make external-python-tarball useful again
Date: Thu, 27 Jan 2011 15:36:34 +0000 [thread overview]
Message-ID: <1296142594.2711.16.camel@scimitar> (raw)
In-Reply-To: <1296142137.27814.7848.camel@rex>
On Thu, 2011-01-27 at 15:28 +0000, Richard Purdie wrote:
> On Thu, 2011-01-27 at 13:09 +0000, Joshua Lock wrote:
> > From: Joshua Lock <josh@linux.intel.com>
> >
> > The attached patch adds the multiprocessing module to the external Python
> > tarball. This is quite useful as we use multiprocessing at recipe parse time
> > now.
>
> Merged into master, thanks!
>
> > This raises two questions:
> > 1) Should we do some testing around the use of multiprocessing?
>
> In what way?
Sorry, what a vague comment. I meant to suggest an exception around the
import and alternative code paths if the module can't be imported.
Or is it safe to assume it exists if you have Python 2.6? - in which
case we just need to improve out Python 2.6 tests so that people can't
run this code on older versions.
>
> > 2) Who can update a new external-python-tarball to the public download?
>
> Beth+me should both have access.
Cool, I'm debugging an issue with package resolution at tarball
generation time, but once that works I'll request a build and upload.
Thanks,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-27 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 13:09 [PATCH 0/1] Make external-python-tarball useful again Joshua Lock
2011-01-27 13:09 ` [PATCH 1/1] external-python-tarball: include multiprocessing module Joshua Lock
2011-01-27 15:28 ` [PATCH 0/1] Make external-python-tarball useful again Richard Purdie
2011-01-27 15:36 ` Joshua Lock [this message]
2011-01-27 17:26 ` Richard Purdie
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=1296142594.2711.16.camel@scimitar \
--to=josh@linux.intel.com \
--cc=poky@yoctoproject.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.