From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mx1.pokylinux.org (Postfix) with ESMTP id 149F94C811BE for ; Thu, 27 Jan 2011 11:26:36 -0600 (CST) Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id p0RHSXaa011980; Thu, 27 Jan 2011 17:28:33 GMT X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gm4zHivVwY6u; Thu, 27 Jan 2011 17:28:32 +0000 (GMT) Received: from [192.168.1.45] (tim [93.97.173.237]) (authenticated bits=0) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id p0RHSRaj011969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 27 Jan 2011 17:28:29 GMT From: Richard Purdie To: Joshua Lock In-Reply-To: <1296142594.2711.16.camel@scimitar> References: <1296142137.27814.7848.camel@rex> <1296142594.2711.16.camel@scimitar> Date: Thu, 27 Jan 2011 17:26:03 +0000 Message-ID: <1296149163.27814.8206.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Cc: poky@yoctoproject.org Subject: Re: [PATCH 0/1] Make external-python-tarball useful again X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2011 17:26:37 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2011-01-27 at 15:36 +0000, Joshua Lock wrote: > 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 > > > > > > 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. Its safe to assume it exists in standard python 2.6. We therefore just need to improve the python 2.6 checks. > > > 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. Sounds good thanks. Richard