Re: [Numpy-discussion] Warnings not raised by np.log in 32 bit build on Windows

On Fri, Aug 23, 2013 at 6:29 AM, Nathaniel Smith wrote: > Probably the thing to do for reliable behaviour is to decide on the > behaviour we want and then implement it "by hand". I.e., either clear the > FP flags inside the ufunc loop (if we decide that log shouldn't raise a > warning), or else c

Re: [Numpy-discussion] Warnings not raised by np.log in 32 bit build on Windows

Probably the thing to do for reliable behaviour is to decide on the behaviour we want and then implement it "by hand". I.e., either clear the FP flags inside the ufunc loop (if we decide that log shouldn't raise a warning), or else check for nan and set the invalid flag ourselves. (Checking for nan

Re: [Numpy-discussion] Warnings not raised by np.log in 32 bit build on Windows

On 8/22/2013 10:32 PM, Warren Weckesser wrote: > Christoph > reported that this code: > > ``` > import numpy as np > > data = np.array([-0.375, -0.25, 0.0]) > s = np.log(data) > ``` > > does not generate two RuntimeWarnings when it is run with numpy 1.7.1 > in a 32 bit Windows 8 environment (numpy

Re: [Numpy-discussion] Warnings not raised by np.log in 32 bit build on Windows

These things may depend on how the compiler implements various calls. Some errors went the other way with Julian's SIMD work, i.e., errors getting set that were not set before. I'm not sure what can be done about it. On Thu, Aug 22, 2013 at 8:32 PM, Warren Weckesser < warren.weckes...@gmail.com>

[Numpy-discussion] Warnings not raised by np.log in 32 bit build on Windows

I'm investigating a test error in scipy 0.13.0 beta 1 that was reported by Christoph Gohlke. The scipy issue is here: https://github.com/scipy/scipy/issues/2771 I don't have a Windows environment to test it myself, but Christoph reported that this code: ``` import numpy as np data = np.array([-

Re: [Numpy-discussion] Warnings and errors while building numpy 1.6.2 on 64 bit system

On Thu, Jul 26, 2012 at 2:29 PM, Prakash Joshi wrote: > Hi All, > > I am building numpy 1.6.2 on 64 bit Mac OSX/CentOS and I found many > warnings and errors of similar kind, however the numpy passes all the > tests. > Please let me know if I can consider this build as good? > > > llvm-gcc-4.2: _

[Numpy-discussion] Warnings and errors while building numpy 1.6.2 on 64 bit system

Hi All, I am building numpy 1.6.2 on 64 bit Mac OSX/CentOS and I found many warnings and errors of similar kind, however the numpy passes all the tests. Please let me know if I can consider this build as good? llvm-gcc-4.2: _configtest.c _configtest.c:5: error: size of array Œtest_array¹ is neg

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Mar 18, 2010, at 4:12 PM, Eric Firing wrote: > Ryan May wrote: >> On Thu, Mar 18, 2010 at 2:46 PM, Christopher Barker >> wrote: >>> Gael Varoquaux wrote: On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: > sure -- that's kind of my point -- if EVERY numpy array were >

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 10:16 PM, Charles R Harris wrote: > On Wed, Mar 17, 2010 at 7:39 PM, Darren Dale wrote: >> On Wed, Mar 17, 2010 at 8:22 PM, Charles R Harris >> > What bothers me here is the opposing desire to separate ufuncs from >> > their >> > ndarray dependency, having them operate on

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Thu, Mar 18, 2010 at 7:26 PM, Christopher Barker wrote: > josef.p...@gmail.com wrote: >>> I'm facing this at the moment: not a big deal, but I'm using histogram2d >>> on some data. I just realized that it may have some NaNs in it, and I >>> have no idea how those are being handled. > >> histogr

Re: [Numpy-discussion] Warnings in numpy.ma.test()

josef.p...@gmail.com wrote: >> I'm facing this at the moment: not a big deal, but I'm using histogram2d >> on some data. I just realized that it may have some NaNs in it, and I >> have no idea how those are being handled. > histogram2d handles neither masked arrays nor arrays with nans > correctly

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Thu, Mar 18, 2010 at 5:12 PM, Eric Firing wrote: > Ryan May wrote: >> On Thu, Mar 18, 2010 at 2:46 PM, Christopher Barker >> wrote: >>> Gael Varoquaux wrote: On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: > sure -- that's kind of my point -- if EVERY numpy array w

Re: [Numpy-discussion] Warnings in numpy.ma.test()

Ryan May wrote: > On Thu, Mar 18, 2010 at 2:46 PM, Christopher Barker > wrote: >> Gael Varoquaux wrote: >>> On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: sure -- that's kind of my point -- if EVERY numpy array were (potentially) masked, then folks would write code t

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Thu, Mar 18, 2010 at 3:46 PM, Christopher Barker wrote: > Gael Varoquaux wrote: >> On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: >>> sure -- that's kind of my point -- if EVERY numpy array were >>> (potentially) masked, then folks would write code to deal with them >>> app

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Thu, Mar 18, 2010 at 2:46 PM, Christopher Barker wrote: > Gael Varoquaux wrote: >> On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: >>> sure -- that's kind of my point -- if EVERY numpy array were >>> (potentially) masked, then folks would write code to deal with them >>> app

Re: [Numpy-discussion] Warnings in numpy.ma.test()

Gael Varoquaux wrote: > On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: >> sure -- that's kind of my point -- if EVERY numpy array were >> (potentially) masked, then folks would write code to deal with them >> appropriately. > > That's pretty much saying: "I have a complicate

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Thu, Mar 18, 2010 at 3:19 PM, Gael Varoquaux wrote: > On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: >> sure -- that's kind of my point -- if EVERY numpy array were >> (potentially) masked, then folks would write code to deal with them >> appropriately. > > That's pretty mu

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: > sure -- that's kind of my point -- if EVERY numpy array were > (potentially) masked, then folks would write code to deal with them > appropriately. That's pretty much saying: "I have a complicated problem and I want every one

Re: [Numpy-discussion] Warnings in numpy.ma.test()

josef.p...@gmail.com wrote: > On Wed, Mar 17, 2010 at 3:12 PM, Christopher Barker >> Given all the limitations of NaN, having a masked >> array is a better way to go, but I'd love it if they were "just there", >> and therefore EVERY numpy function and package built on numpy would >> handle them gr

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Mar 18, 2010, at 11:03 AM, Bruce Southey wrote: > On 03/17/2010 04:20 PM, Pierre GM wrote: >> On Mar 17, 2010, at 11:09 AM, Bruce Southey wrote: >> >>> On 03/17/2010 01:07 AM, Pierre GM wrote: >>> All, As you're probably aware, the current test suite for numpy.ma raises some na

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Mar 17, 2010, at 9:16 PM, Charles R Harris wrote: > > > On Wed, Mar 17, 2010 at 7:39 PM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 8:22 PM, Charles R Harris > wrote: > > > > What bothers me here is the opposing desire to separate ufuncs from their > > ndarray dependency, having them opera

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On 03/17/2010 04:20 PM, Pierre GM wrote: > On Mar 17, 2010, at 11:09 AM, Bruce Southey wrote: > >> On 03/17/2010 01:07 AM, Pierre GM wrote: >> >>> All, >>> As you're probably aware, the current test suite for numpy.ma raises some >>> nagging warnings such as "invalid value in ...". These

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Mar 17, 2010, at 5:43 PM, Charles R Harris wrote: > > > > On Wed, Mar 17, 2010 at 3:13 PM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM wrote: > > On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: > >> > >> I started thinking about a third method called __input_prepare__ th

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Mar 17, 2010, at 3:18 PM, josef.p...@gmail.com wrote: > On Wed, Mar 17, 2010 at 3:12 PM, Christopher Barker > wrote: >> >> One of the things I liked about MATLAB was that NaNs were well handled >> almost all the time. Given all the limitations of NaN, having a masked >> array is a better way t

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Mar 17, 2010, at 11:09 AM, Bruce Southey wrote: > On 03/17/2010 01:07 AM, Pierre GM wrote: >> All, >> As you're probably aware, the current test suite for numpy.ma raises some >> nagging warnings such as "invalid value in ...". These warnings are only >> issued when a standard numpy ufunc (eg.

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 7:39 PM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 8:22 PM, Charles R Harris > wrote: > > > > > > On Wed, Mar 17, 2010 at 5:26 PM, Darren Dale wrote: > >> > >> On Wed, Mar 17, 2010 at 5:43 PM, Charles R Harris > >> wrote: > >> > On Wed, Mar 17, 2010 at 3:13 PM, Darre

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 8:22 PM, Charles R Harris wrote: > > > On Wed, Mar 17, 2010 at 5:26 PM, Darren Dale wrote: >> >> On Wed, Mar 17, 2010 at 5:43 PM, Charles R Harris >> wrote: >> > On Wed, Mar 17, 2010 at 3:13 PM, Darren Dale wrote: >> >> On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM >> >> w

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 5:26 PM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 5:43 PM, Charles R Harris > wrote: > > On Wed, Mar 17, 2010 at 3:13 PM, Darren Dale wrote: > >> On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM > wrote: > >> > On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: > >> >> > >>

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 5:43 PM, Charles R Harris wrote: > On Wed, Mar 17, 2010 at 3:13 PM, Darren Dale wrote: >> On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM wrote: >> > On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: >> >> >> >> I started thinking about a third method called __input_prepare__ th

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 3:13 PM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM wrote: > > On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: > >> > >> I started thinking about a third method called __input_prepare__ that > >> would be called on the way into the ufunc, which would

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM wrote: > On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: >> >> I started thinking about a third method called __input_prepare__ that >> would be called on the way into the ufunc, which would allow you to >> intercept the input and pass a somehow modified

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: > > I started thinking about a third method called __input_prepare__ that > would be called on the way into the ufunc, which would allow you to > intercept the input and pass a somehow modified copy back to the > ufunc. The total flow would be: > >

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 3:12 PM, Christopher Barker wrote: > Eric Firing wrote: >> My motivation for going >> to the C level was speed and control; many ma operations are very slow >> compared to their numpy counterparts, and moving the mask handling to C >> can erase nearly all of this penalty. >

Re: [Numpy-discussion] Warnings in numpy.ma.test()

Eric Firing wrote: > My motivation for going > to the C level was speed and control; many ma operations are very slow > compared to their numpy counterparts, and moving the mask handling to C > can erase nearly all of this penalty. really? very cool. I was thinking about this the other day, and

Re: [Numpy-discussion] Warnings in numpy.ma.test()

Charles R Harris wrote: > > > On Wed, Mar 17, 2010 at 6:19 AM, Darren Dale > wrote: > > On Wed, Mar 17, 2010 at 2:07 AM, Pierre GM > wrote: > > All, > > As you're probably aware, the current test suite for numpy.ma >

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 10:45 AM, Charles R Harris wrote: > > > On Wed, Mar 17, 2010 at 6:19 AM, Darren Dale wrote: >> >> On Wed, Mar 17, 2010 at 2:07 AM, Pierre GM wrote: >> > All, >> > As you're probably aware, the current test suite for numpy.ma raises >> > some nagging warnings such as "inva

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 9:20 AM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 10:11 AM, Ryan May wrote: >> On Wed, Mar 17, 2010 at 7:19 AM, Darren Dale wrote: >>> Is this general enough for your use case? I haven't tried to think >>> about how to change some global state at one point and change

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On 03/17/2010 01:07 AM, Pierre GM wrote: > All, > As you're probably aware, the current test suite for numpy.ma raises some > nagging warnings such as "invalid value in ...". These warnings are only > issued when a standard numpy ufunc (eg., np.sqrt) is called on a MaskedArray, > instead of its

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 6:19 AM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 2:07 AM, Pierre GM wrote: > > All, > > As you're probably aware, the current test suite for numpy.ma raises > some nagging warnings such as "invalid value in ...". These warnings are > only issued when a standard numpy

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 10:11 AM, Ryan May wrote: > On Wed, Mar 17, 2010 at 7:19 AM, Darren Dale wrote: >> Is this general enough for your use case? I haven't tried to think >> about how to change some global state at one point and change it back >> at another, that seems like a bad idea and diff

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 7:19 AM, Darren Dale wrote: > Is this general enough for your use case? I haven't tried to think > about how to change some global state at one point and change it back > at another, that seems like a bad idea and difficult to support. Sounds like the textbook use case for

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 2:07 AM, Pierre GM wrote: > All, > As you're probably aware, the current test suite for numpy.ma raises some > nagging warnings such as "invalid value in ...". These warnings are only > issued when a standard numpy ufunc (eg., np.sqrt) is called on a MaskedArray, > inste

[Numpy-discussion] Warnings in numpy.ma.test()

All, As you're probably aware, the current test suite for numpy.ma raises some nagging warnings such as "invalid value in ...". These warnings are only issued when a standard numpy ufunc (eg., np.sqrt) is called on a MaskedArray, instead of its numpy.ma (eg., np.ma.sqrt) equivalent. The reason i

Re: [Numpy-discussion] Warnings in current trunk

On Tue, Feb 17, 2009 at 11:37 PM, David Cournapeau < da...@ar.media.kyoto-u.ac.jp> wrote: > Charles R Harris wrote: > > > > Oh, and this should be avoided: > > > > if (endptr != NULL) *endptr = (char*)p; > > > > Folks have different views about whether the single statement should > > be in

Re: [Numpy-discussion] Warnings in current trunk

Charles R Harris wrote: > > Oh, and this should be avoided: > > if (endptr != NULL) *endptr = (char*)p; > > Folks have different views about whether the single statement should > be in brackets but no one recommends putting it on the same line as > the if. It's too easy to overlook and habi

Re: [Numpy-discussion] Warnings in current trunk

On Tue, Feb 17, 2009 at 11:14 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Tue, Feb 17, 2009 at 10:22 PM, David Cournapeau < > da...@ar.media.kyoto-u.ac.jp> wrote: > >> Charles R Harris wrote: >> > >> > >> > On Tue, Feb 17, 2009 at 8:56 PM, David Cournapeau >> > mailto:da...@a

Re: [Numpy-discussion] Warnings in current trunk

On Tue, Feb 17, 2009 at 10:22 PM, David Cournapeau < da...@ar.media.kyoto-u.ac.jp> wrote: > Charles R Harris wrote: > > > > > > On Tue, Feb 17, 2009 at 8:56 PM, David Cournapeau > > mailto:da...@ar.media.kyoto-u.ac.jp>> > > wrote: > > > > Charles R Harris wrote: > > > I see a lot of warnin

Re: [Numpy-discussion] Warnings in current trunk

Charles R Harris wrote: > > > On Tue, Feb 17, 2009 at 8:56 PM, David Cournapeau > mailto:da...@ar.media.kyoto-u.ac.jp>> > wrote: > > Charles R Harris wrote: > > I see a lot of warnings like: > > > > In file included from numpy/core/src/multiarraymodule.c:87: > > numpy/core/src/u

Re: [Numpy-discussion] Warnings in current trunk

On Tue, Feb 17, 2009 at 8:56 PM, David Cournapeau < da...@ar.media.kyoto-u.ac.jp> wrote: > Charles R Harris wrote: > > I see a lot of warnings like: > > > > In file included from numpy/core/src/multiarraymodule.c:87: > > numpy/core/src/umath_funcs_c99.inc.src:199:1: warning: "isnan" redefined > >

Re: [Numpy-discussion] Warnings in current trunk

David Cournapeau wrote: > Charles R Harris wrote: > >> I see a lot of warnings like: >> >> In file included from numpy/core/src/multiarraymodule.c:87: >> numpy/core/src/umath_funcs_c99.inc.src:199:1: warning: "isnan" redefined >> In file included from /usr/include/python2.5/pyport.h:204, >>

Re: [Numpy-discussion] Warnings in current trunk

Charles R Harris wrote: > I see a lot of warnings like: > > In file included from numpy/core/src/multiarraymodule.c:87: > numpy/core/src/umath_funcs_c99.inc.src:199:1: warning: "isnan" redefined > In file included from /usr/include/python2.5/pyport.h:204, > from /usr/include/python

[Numpy-discussion] Warnings in current trunk

I see a lot of warnings like: In file included from numpy/core/src/multiarraymodule.c:87: numpy/core/src/umath_funcs_c99.inc.src:199:1: warning: "isnan" redefined In file included from /usr/include/python2.5/pyport.h:204, from /usr/include/python2.5/Python.h:57, f

[Numpy-discussion] Warnings for Travis

Hi Travis, The following turned up on the 64-bit windows buildbot. I don't know what triggers them as they don't normally show, but they look legit. numpy\core\src\ufuncobject.c(1700) : warning C4244: '=' : conversion from 'npy_intp' to 'int', possible loss of data numpy\core\src\ufuncobject.c(17

Re: [Numpy-discussion] Warnings as exceptions?

On Nov 13, 2007 11:48 AM, Michael McNeil Forbes <[EMAIL PROTECTED]> wrote: > On 13 Nov 2007, at 8:46 AM, Travis E. Oliphant wrote: > > > Michael McNeil Forbes wrote: > >> Why are numpy warnings printed rather than issued using the standard > >> warnings library? ... in util.py ... > > The "warn" o

Re: [Numpy-discussion] Warnings as exceptions?

On 13 Nov 2007, at 8:46 AM, Travis E. Oliphant wrote: > Michael McNeil Forbes wrote: >> Why are numpy warnings printed rather than issued using the standard >> warnings library? ... in util.py ... > The "warn" option explicitly allows you to use the warnings library. > There is already the "print"

Re: [Numpy-discussion] Warnings as exceptions?

Michael McNeil Forbes wrote: > Why are numpy warnings printed rather than issued using the standard > warnings library? I know that the behaviour can be controlled by > seterr(), but it seem rather unpythonic not to use the warnings library. > > The "warn" option explicitly allows you to us

Re: [Numpy-discussion] Warnings as exceptions?

On Nov 10, 2007 3:33 PM, Michael McNeil Forbes <[EMAIL PROTECTED]> wrote: > Why are numpy warnings printed rather than issued using the standard > warnings library? I know that the behaviour can be controlled by > seterr(), but it seem rather unpythonic not to use the warnings library. > > Is the

[Numpy-discussion] Warnings as exceptions?

Why are numpy warnings printed rather than issued using the standard warnings library? I know that the behaviour can be controlled by seterr(), but it seem rather unpythonic not to use the warnings library. Is there an explicit reason for this choice? (It seems like a pretty trivial modifi

[Numpy-discussion] Warnings

How can I get the line number of where a numpy warning message is envoked in my code? Cheers Tommy ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion