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