From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 5/18] gnu: Add python-pytest-xdist. Date: Fri, 19 Feb 2016 23:40:07 -0500 Message-ID: <20160220044007.GC14995@jasmine> References: <87k2m5sgep.fsf@dustycloud.org> <87io1knmcz.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47740) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWzL3-0006aq-7h for guix-devel@gnu.org; Fri, 19 Feb 2016 23:40:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aWzL0-0003Pd-0L for guix-devel@gnu.org; Fri, 19 Feb 2016 23:40:13 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:43181) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWzKz-0003PV-TD for guix-devel@gnu.org; Fri, 19 Feb 2016 23:40:09 -0500 Content-Disposition: inline In-Reply-To: <87io1knmcz.fsf@dustycloud.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Christopher Allan Webber Cc: guix-devel@gnu.org On Fri, Feb 19, 2016 at 06:31:28PM -0800, Christopher Allan Webber wrote: > Updated. > > From 5930defefa4c7966afd1c20f66d22c8b95bf024f Mon Sep 17 00:00:00 2001 > From: Christopher Allan Webber > Date: Sat, 13 Feb 2016 18:11:47 -0800 > Subject: [PATCH 04/18] gnu: Add python-pytest-xdist. > > * gnu/packages/python.scm (python-pytest-xdist, python2-pytest-xdist): > New variables. > --- > gnu/packages/python.scm | 36 ++++++++++++++++++++++++++++++++++++ > 1 file changed, 36 insertions(+) > > diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm > index a5d42f5..a6823bc 100644 > --- a/gnu/packages/python.scm > +++ b/gnu/packages/python.scm > @@ -1665,6 +1665,42 @@ supports coverage of subprocesses.") > (define-public python2-pytest-runner > (package-with-python2 python-pytest-runner)) > > +(define-public python-pytest-xdist > + (package > + (name "python-pytest-xdist") > + (version "1.14") > + (source > + (origin > + (method url-fetch) > + (uri (pypi-uri "pytest-xdist" version ".zip")) > + (sha256 > + (base32 > + "08rn2l39ds60xshs4js787l84pfckksqklfq2wq9x8ig2aci2pja")))) > + (build-system python-build-system) > + (native-inputs > + `(("unzip" ,unzip))) > + (propagated-inputs > + `(("python-setuptools" ,python-setuptools) > + ("python-setuptools-scm" ,python-setuptools-scm) > + ("python-execnet" ,python-execnet) > + ("python-pytest" ,python-pytest) > + ("python-py" ,python-py))) I see how it could make sense for a testing program, but I just want to be sure; should setuptools and pytest be propagated? > + (home-page > + "https://github.com/pytest-dev/pytest-xdist") > + (synopsis > + "Plugin for py.test with distributed testing and loop-on-failing modes") > + (description > + "The pytest-xdist plugin extends py.test with some unique test execution > +modes: parallelization, running tests in boxed subprocesses, the ability > +to run tests repeatedly when failed, and the ability to run tests on multiple > +Python interpreters or platforms. It uses rsync to copy the existing > +program code to a remote location, executes there, and then syncs the > +result back.") > + (license license:expat))) > + > +(define-public python2-pytest-xdist > + (package-with-python2 python-pytest-xdist)) > + > (define-public python-scripttest > (package > (name "python-scripttest") > -- > 2.6.3 >