[Numpy-discussion] Request for testing

josef.pktd@gmai... josef.pktd@gmai...
Sun Feb 21 10:27:07 CST 2010


On Sun, Feb 21, 2010 at 11:05 AM, Charles R Harris
<charlesr.harris@gmail.com> wrote:
>
>
> On Sun, Feb 21, 2010 at 3:33 AM, David Cournapeau <cournape@gmail.com>
> wrote:
>>
>> On Sun, Feb 21, 2010 at 7:30 PM, Charles R Harris
>> <charlesr.harris@gmail.com> wrote:
>> > Hi All,
>> >
>> > I would be much obliged if some folks would run the attached script and
>> > report the output, numpy version, and python version. It just runs
>> > np.isinf(np.inf), which raises an "invalid value" warning with current
>> > numpy. As far as I can see the function itself hasn't changed since
>> > numpy1.3, yet numpy1.3 & python2.5 gives no such warning.

no warning WinXP, numpy 1.4.0 superpack (I think)

>isinf.py
True

Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> numpy.version.version
'1.4.0'

Josef

>>
>> This is most likely a bug in isinf or how we use it - the warning is
>> not new, but was hidden before because of the FPU error stage set to
>> ignore instead of warning. I am afraid dealing with this correctly
>> cannot be done in a short time frame: the issues are quite subtle, and
>> very platform dependent.
>>
>
> The script enables the warning so the difference shouldn't depend on the
> recent change in the warnings default. I was thinking it more likely had
> something to do with the build environment/python version/compiler
> flags/.etc.
>
> Chuck
>
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>


More information about the NumPy-Discussion mailing list