Il giorno gio, 19/01/2017 alle 15.19 +, Ghislain Vaillant ha
scritto:
> On Thu, 2017-01-19 at 15:55 +0100, Pietro Battiston wrote:
> > Il giorno mar, 17/01/2017 alle 23.26 +, Ghislain Vaillant ha
> > scritto:
> > [...]
> > > Assuming, numpy stays in this version for the release, i.e.
> > >
On Thu, 2017-01-19 at 15:55 +0100, Pietro Battiston wrote:
> Il giorno mar, 17/01/2017 alle 23.26 +, Ghislain Vaillant ha
> scritto:
> > On Tue, 2017-01-17 at 22:35 +0100, Pietro Battiston wrote:
> > > [...]
> > > I am a bit confused. It seems to me that bottleneck itself is not
> > > in
> > >
Il giorno mar, 17/01/2017 alle 23.26 +, Ghislain Vaillant ha
scritto:
> On Tue, 2017-01-17 at 22:35 +0100, Pietro Battiston wrote:
> > [...]
> > I am a bit confused. It seems to me that bottleneck itself is not
> > in
> > worse shape than before the numpy regression was introduced.
>
> It is
control: block -1 by 851858
On Tue, 2017-01-17 at 22:35 +0100, Pietro Battiston wrote:
> Il giorno mar, 17/01/2017 alle 18.24 +, Ghislain Vaillant ha
> scritto:
> > [...]
> > There are 2 options:
> >
> > 1) Do an upload with tests enabled, knowing it would FTBFS, and file
> > an
> > RC for it. Once numpy gets eventually
Thanks for your report. Tests run fine in my install, which is a bit
out of date (e.g. python3-numpy version 1:1.11.2-1).
I will try to understand what update broke them. In the meanwhile, I
filed the bug upstream.
Pietro
Il giorno lun, 16/01/2017 alle 20.50 +, Ghislain Antony Vaillant ha
scritto:
> [...]
> Input array:
> [[ inf 7. -inf -9.]
> [-10. nan nan 5.]
> [ 4. nan nan inf]]
>
> x and y +inf location mismatch:
> x: array([-1. , -2.5, inf], dtype=float32)
> y: array([-1. , -2.5, 2. ],
Il giorno lun, 16/01/2017 alle 22.32 +, Ghislain Vaillant ha
scritto:
> [...]
> Just out of curiosity, may I ask why the package is not team-
> maintained
> by the Python modules team or the Debian Science team?
No specific reason, except that I don't know how it works and don't
have much
On Mon, 2017-01-16 at 23:17 +0100, Pietro Battiston wrote:
> Thanks for your report. Tests run fine in my install, which is a bit
> out of date (e.g. python3-numpy version 1:1.11.2-1).
Mine has 1:1.12.0~rc2.
> I will try to understand what update broke them. In the meanwhile, I
> filed the bug
Package: src:bottleneck
Severity: important
Dear Maintainer,
In my attempt to investigate why xarray fails to test with the packaged
bottleneck [1], I have looked at its packaging and enabled the test suite by
adding the missing b-deps on python[,3]-nose.
[1]
10 matches
Mail list logo
