I think arange for complex numbers should work like meshgrid,
with the real and imaginary axis replacing the x and y axis. That would
mean something like this:
def complex_arange(start,end,stride):
def iscomplex(x):
if ((type(x)==complex) or (type(x)==complex64)
or (type(x)==co
Russel Howe wrote:
>> arange(1j, 5j, 1) do? Numeric raises an exception here, and I thing
>> numpy
>> should, too.
>
> The same as arange(1, 5, 1j) - an empty array since it takes 0 of the
> step to cross the distance.
I'm not sure that's really the answer. I think it's simply not defined. N
> arange(1j, 5j, 1) do? Numeric raises an exception here, and I thing
> numpy
> should, too.
>
The same as arange(1, 5, 1j) - an empty array since it takes 0 of the
step to cross the distance. But something like
arange(1j, 5j, 1j) seems fine. As does arange(1j, 3+5j, 2+1j) which
should gi
On 2/1/07, Robert Kern <[EMAIL PROTECTED]> wrote:
Russel Howe wrote:
(It's good to see so many Rudds seeing sense and using Python and
numpy. ;-))
rudds! Here? Dear me.
--
//=][=\\
[EMAIL PROTECTED]
___
Numpy-discussion mailing list
Numpy-disc
Russel Howe wrote:
(It's good to see so many Rudds seeing sense and using Python and numpy. ;-))
> Should this work?
>
> Python 2.4.3 (#1, Dec 27 2006, 21:18:13)
> [GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
>
Should this work?
Python 2.4.3 (#1, Dec 27 2006, 21:18:13)
[GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy as N
>>> N.__version__
'1.0.2.dev3531'
>>> N.arange(1j, 5j)
array([], dtype=complex128)
>>>
