From: Francesc A. <fa...@ca...> - 2006-11-02 19:26:44
|
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, -- Francesc Altet | Be careful about using the following code -- Carabos Coop. V. | I've only proven that it works, www.carabos.com | I haven't tested it. -- Donald Knuth |
From: Todd M. <jm...@st...> - 2006-11-02 21:04:57
Attachments:
slice64.patch
|
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, > > |
From: A. M. A. <per...@gm...> - 2006-11-02 21:26:11
|
On 02/11/06, Francesc Altet <fa...@ca...> 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 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. Someone has to say it: you could just drop support for the obsolete numarray and provide only support for its successor, numpy. A. M. Archibald |
From: Francesc A. <fa...@ca...> - 2006-11-03 15:52:13
|
A Dijous 02 Novembre 2006 22:26, A. M. Archibald escrigu=E9: > On 02/11/06, Francesc Altet <fa...@ca...> 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 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. > > Someone has to say it: you could just drop support for the obsolete > numarray and provide only support for its successor, numpy. Yeah, that would be the easy path, agreed. However, only God knows how many code out there exists that still uses numarray (or Numeric). We were optimistic that, given the implementation of the stunningly efficient and easy-to-use array protocol in the three packages (NumPy, numarray and Numeric), that very much boosted the interoperability between them, support for all three would be a relatively easy thing to keep in next release PyTables (with NumPy at its core). Unfortunately, time has demonstrated how easy for a package to become obsolete (and hence, useless) is. Just a new version of Python (2.5 this time) and the advent of 64-bit platforms has rendered obsolete both numarray and Numeric in one shot. Mmm, perhaps it would make more sense to support just numarray (and Numeric up to an extend) in just 32-bit platforms, but again, even that could be risky. Well, "que sera, sera..." only time will say (as the song says). Cheers, =2D-=20 >0,0< Francesc Altet =A0 =A0 http://www.carabos.com/ V V C=E1rabos Coop. V. =A0=A0Enjoy Data "-" |