Hey Numeric people!
I am just upgrading to a more recent version of Numeric and observe a new behaviour:
Python 1.5.2 (#9, May 30 2000, 15:08:12) [GCC 2.95.2 19991024 (release)] on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam Hello from .pythonrc.py
import Numeric Numeric.__version__
'11'
Numeric.arange(2)*1j
Segmentation fault
Python 1.5.1 (#1, Dec 17 1998, 20:58:15) [GCC 2.7.2.3] on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam Hello from .pythonrc.py
import Numeric Numeric.__version__
'1.7'
Numeric.arange(2)*1j
array([ 0.+0.j, 0.+1.j])
I also saw: Numerical Python - Bug Tracking Viewing Open Bugs Bug ID Summary 102277 CFLOAT/DOUBLE_setitem crashes when accessing imag. part
Am I hitting that bug?
CU
Jean-Bernard
Jean-Bernard Addor writes:
Hey Numeric people!
Python 1.5.2 (#9, May 30 2000, 15:08:12) [GCC 2.95.2 19991024 (release)] on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam Hello from .pythonrc.py
import Numeric Numeric.__version__
'11'
Numeric.arange(2)*1j
Segmentation fault
This seems to be fixed in the current CVS version. I suggest you either wait for the next release or grab the current version from CVS if this is really a problem for you.
Python 1.6a2 (#9, May 22 2000, 12:34:51) [GCC 2.95.2 19991024 (release)] on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam Copyright 1995-2000 Corporation for National Research Initiatives (CNRI)
import Numeric Numeric.__version__
'15.2'
Numeric.arange(2)*1j
array([ 0.+0.j, 0.+1.j])
Hey Numpy people!
On Fri, 2 Jun 2000, Charles G Waldman wrote:
This seems to be fixed in the current CVS version. I suggest you either wait for the next release or grab the current version from CVS if this is really a problem for you.
I don't understand wich files I would need to take a new version from and wich command I have to issue to get a version of Numpy that correct the bug I just hit.
Thanks for help.
I would like my code to work with the next release.
Jean-Bernard