A Dijous 02 Novembre 2006 22:26, A. M. Archibald escrigué:
> On 02/11/06, Francesc Altet <[EMAIL PROTECTED]> wrote:
> > 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
On 02/11/06, Francesc Altet <[EMAIL PROTECTED]> wrote:
> 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 addres
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 term
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 see
