Re: [Numpy-discussion] Request for testing
On Sun, Feb 21, 2010 at 4:30 AM, Charles R Harris charlesr.har...@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. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion lesserwhi...@microsat-xps ~/Desktop $ python isinf.py Warning: invalid value encountered in isinf True Platform : Linux microsat-xps 2.6.31-gentoo-r6 (x86_64 Intel(R) Core(TM)2 Duo CPU T5450) Python : Python 2.6.4 (r264:75706, Dec 7 2009, 11:36:55) NumPy : 2.0.0.dev8251 GCC : gcc (Gentoo 4.3.4 p1.0, pie-10.1.5) 4.3.4 glibc : 2.10.1 Sean ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
I have several Pythons with several numpys on it: (Ordered by version:) 1. python-2.4 isinf.py True Python 2.4.1 (#65, Mar 30 2005, 09:13:57) [MSC v.1310 32 bit (Intel)] on win32 Type help, copyright, credits or license for more information. import numpy numpy.__version__ '1.1.1' 2. python-2.5 isinf.py True Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)] on win32 Type help, copyright, credits or license for more information. import numpy numpy.__version__ '1.4.0' 3. python-2.6 isinf.py True Python 2.6.3 (r263rc1:75186, Oct 2 2009, 20:40:30) [MSC v.1500 32 bit (Intel)] on win32 Type help, copyright, credits or license for more information. import numpy numpy.__version__ '1.3.0' Friedrich ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Request for testing
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.
Chuck
import numpy as np
import warnings
warnings.simplefilter('always')
np.seterr(invalid='print')
print (np.isinf(np.inf))
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On Sun, Feb 21, 2010 at 7:30 PM, Charles R Harris charlesr.har...@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. 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. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On Sun, 21 Feb 2010 03:30:31 -0700
Charles R Harris charlesr.har...@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.
Chuck
python -i isinf.py
2.0.0.dev8233
2.6.2
import numpy as np
import warnings
import platform
print np.__version__
print platform.python_version()
warnings.simplefilter('always')
np.seterr(invalid='print')
print (np.isinf(np.inf))
Nils
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On 2/21/2010 5:30 AM, Charles R Harris wrote:
I would be much obliged if some folks would run the attached script and
report the output, numpy version, and python version.
No problem with NumPy 1.3.0 (from superpack) on Python 2.6.4 under Vista.
Alan Isaac
Python 2.6.4 (r264:75708, Oct 26 2009, 08:23:19) [MSC v.1500 32 bit (Intel)] on
win32
Type help, copyright, credits or license for more information.
import numpy as np
import warnings
warnings.simplefilter('always')
np.seterr(invalid='print')
{'over': 'ignore', 'divide': 'ignore', 'invalid': 'ignore', 'under': 'ignore'}
print (np.isinf(np.inf))
True
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
My machine is a PPC dual G5, running Mac OS X 10.5.8
~ $ python
Python 2.5.4 (r254:67917, Dec 23 2008, 14:57:27)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type help, copyright, credits or license for more information.
import numpy as np
import warnings
warnings.simplefilter('always')
np.seterr(invalid='print')
{'over': 'ignore', 'divide': 'ignore', 'invalid': 'ignore', 'under':
'ignore'}
print (np.isinf(np.inf))
True
np.__version__
'1.4.0.dev7577'
On Feb 21, 2010, at 5:30 AM, Charles R Harris 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.
Chuck
isinf.py___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On Sun, Feb 21, 2010 at 6:30 PM, Charles R Harris charlesr.har...@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. $ python isinf.py Warning: invalid value encountered in isinf True Python 2.6.4, on Snow Leopard NumPy trunk r8233 Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On Sun, Feb 21, 2010 at 2:30 AM, Charles R Harris charlesr.har...@gmail.com wrote: I would be much obliged if some folks would run the attached script and report the output, numpy version, and python version. import isinf Warning: invalid value encountered in isinf True Python 2.6.4 (r264:75706, Dec 7 2009, 18:43:55) [GCC 4.4.1] on linux2 Numpy '1.4.0rc2' ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On Sun, Feb 21, 2010 at 3:33 AM, David Cournapeau courn...@gmail.comwrote: On Sun, Feb 21, 2010 at 7:30 PM, Charles R Harris charlesr.har...@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. 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
Re: [Numpy-discussion] Request for testing
Charles R Harris 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. Python 2.5.4 on Mac OSX 10.5.8 (EPD 5.0.0): I do not get a warning with numpy 1.3.0 or 2.0.0.dev8233. Warren ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On Sun, Feb 21, 2010 at 5:30 AM, Charles R Harris charlesr.har...@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. Chuck On Kubuntu 9.10 with recent trunk. $ python2.5 isinf.py True $ python2.6 isinf.py Warning: invalid value encountered in isinf True Skipper PS. I also see a lot of the divide by zero warnings now (which are helpful) and wondered if they weren't related. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
Charles R Harris 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. Chuck efir...@manini:~$ python test/isinf.py Warning: invalid value encountered in isinf True In [4]:numpy.version.version Out[4]:'1.5.0.dev8042' Python 2.6.4 (r264:75706, Dec 7 2009, 18:45:15) Ubuntu 9.10 Eric ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
$ python isinf.py Warning: invalid value encountered in isinf True machine: gentoo linux on amd64 python 2.6.4 (64 bit) gcc 4.3.4 numpy.__version__ == '1.4.0' glibc 2.10.1 Nadav -Original Message- From: numpy-discussion-boun...@scipy.org on behalf of Charles R Harris Sent: Sun 21-Feb-10 12:30 To: numpy-discussion Subject: [Numpy-discussion] Request for testing 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. Chuck winmail.dat___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
On Sun, Feb 21, 2010 at 4:30 AM, Charles R Harris charlesr.har...@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.
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
[gse...@ccn ~]$ python isinf.py
True
[gse...@ccn various]$ python sysinfo.py
Platform :
Linux-2.6.31.9-174.fc12.i686.PAE-i686-with-fedora-12-Constantine
Python : ('CPython', 'tags/r262', '71600')
NumPy : 1.5.0.dev8038
--
Gökhan
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Request for testing
No Warning for me:
└─(08:26 $)─ python isinf.py
True
└─(08:26 $)─ python2.5 isinf.py
True
Python 2.6.4 (r264:75706, Dec 7 2009, 18:43:55)
[GCC 4.4.1] on linux2
Python 2.5.4 (r254:67916, Jan 20 2010, 21:43:02)
[GCC 4.4.1] on linux2
numpy.version.version
'1.3.0'
└─(08:33 $)─ uname -a
Linux cudos0803 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 02:39:34 UTC 2010
x86_64 GNU/Linux
└─(08:31 $)─ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 9.10
Release: 9.10
Codename: karmic
On 02/21/10 03:30, Charles R Harris 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.
Chuck
import numpy as np
import warnings
warnings.simplefilter('always')
np.seterr(invalid='print')
print (np.isinf(np.inf))
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
