GNU bug report logs - #25834
Update scientific Python packages

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#25834: closed (Update scientific Python packages)
Date: Mon, 06 Mar 2017 22:54:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 06 Mar 2017 23:53:42 +0100
with message-id <87y3wi2f0p.fsf <at> kirby.i-did-not-set--mail-host-address--so-tickle-me>
and subject line Re: bug#25834: [PATCH] Update scipy stack.
has caused the debbugs.gnu.org bug report #25834,
regarding Update scientific Python packages
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
25834: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25834
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Thomas Danckaert <post <at> thomasdanckaert.be>
To: guix-patches <at> gnu.org
Subject: Update scientific Python packages
Date: Wed, 22 Feb 2017 11:30:15 +0100 (CET)

Hi,

I'm submitting a patch series to update numpy, matplotlib, scipy and 
ipython.  I've split out the documentation for numpy and matplotlib 
into separate packages to avoid issues with the following cyclic 
dependencies:

 - numpy documentation depends on matplotlib, which depends on numpy.

 - documentation for the new version of matplotlib also depends on
   ipython, which depends on matplotlib and numpy.

If the preference is to work with multiple outputs instead, I can 
work out something with “bootstrap” packages and 
package-input-rewriting, but I like the simplicity of separate 
documentation packages (which also avoids repeatedly building the 
same package for bootstrapping purposes).

Thomas

[Message part 3 (message/rfc822, inline)]

From: Marius Bakke <mbakke <at> fastmail.com>
To: Thomas Danckaert <post <at> thomasdanckaert.be>
Cc: dannym <at> scratchpost.org, 25834-done <at> debbugs.gnu.org
Subject: Re: bug#25834: [PATCH] Update scipy stack.
Date: Mon, 06 Mar 2017 23:53:42 +0100

[Message part 4 (text/plain, inline)]

Thomas Danckaert <post <at> thomasdanckaert.be> writes:

> From: Marius Bakke <mbakke <at> fastmail.com>
> Subject: Re: bug#25834: [PATCH] Update scipy stack.
> Date: Mon, 06 Mar 2017 14:25:26 +0100
>
>> Please pay attention during the 'check' phase of Python packages -- 
>> both
>> colorspacious and the shutils backport prints 'Ran 0 tests in...'.
>> Usually this is a sign that they require some other command than 
>> 'python
>> setup.py test', which is the default of python-build-system.
>>
>> I pushed a fix for python2-backports-shutil-get-terminal-size that 
>> I had
>> in my queue, but it would be nice to enable tests on colorspacious 
>> as
>> well. Any takers? :)
>
> I've attached an attempt (now runs 34 tests).  Am I right that 
> running “nosetests colorspacious/*.py” is the only way to make it run 
> the tests in this case?

Thanks! By adding "--all-modules" to the "nosetests" invocation, it was
able to discover the tests without having to add them as arguments.

Pushed! Closing this bug now, wahoo!

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.