Re: [Numpy-discussion] numarray indexing problems with Python2.5 and 64-bit platforms

[Todd M. <jm...@st...>]

Here's a stab at a solution but I don't have easy access to 64-bit linux 
at the moment so it is untested.   If someone is willing to test it 
(and/or fix it) I'll add it to the next numarray release.  It should be 
noted that numarray is not 64-bit enabled (it compiles as a 32-bit 
program in terms of arrays) which is another motivation to switch to numpy.

Regards,
Todd

Francesc Altet wrote:
> Hi,
>
> I've detected that numarray (1.5.2) seems to be bitten by the change in
> Python 2.5 for indexes (http://docs.python.org/whatsnew/pep-353.html). 
> In a Linux64 machine (using Python 2.5), I get this:
>
>   
>>>> a=numarray.array([1,2,3])
>>>> a[1:2]
>>>>         
> array([1, 2])  # !
>
> However, both Numeric and numpy seems to work well with the same
> scenario.
>
>   
>>>> b=Numeric.array([1,2,3])
>>>> b[1:2]
>>>>         
> array([2])
>   
>>>> c=numpy.array([1,2])
>>>> c[1:2]
>>>>         
> array([2])
>
> I see this as a major issue in numarray and poses in great danger the
> intended support of PyTables for numarray that we planned for some time
> (until end of 2007). It would be nice to know if the numarray crew would
> be willing to address this, or, now that NumPy 1.0 is out, they have
> decided to completely drop the support for it.
>
> We'd really like to continue offering support for numarray (in the end,
> it is a very good piece of software) in PyTables, but don't having a
> solution for this problem anytime soon, will make this very problematic
> to us.
>
> Thanks,
>
>