Removal of numarray and oldnumeric packages.
Hi All, I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never... Chuck
On 23.09.2013, at 7:03PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
The only thing I'd care about is the nd_image subpackage, but as far as I can see, that's already just a wrapper to import scipy.ndimage. I take it there are no pure numpy implementations for the likes of map_coordinates, right? Cheers, Derek
On Mon, Sep 23, 2013 at 11:21 AM, Derek Homeier < derek@astro.physik.uni-goettingen.de> wrote:
On 23.09.2013, at 7:03PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
The only thing I'd care about is the nd_image subpackage, but as far as I can see, that's already just a wrapper to import scipy.ndimage. I take it there are no pure numpy implementations for the likes of map_coordinates, right?
As far as I know, that is correct. Chuck
We at STScI have no objection. If we have any residual dependencies, we'll then find out and fix them. Perry On Sep 23, 2013, at 1:03 PM, Charles R Harris wrote:
Hi All,
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
Chuck _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
Hi All,
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
Chuck
Hi Chuck, Could you clarify how we'd know if this is a problem in a large package? i.e. Is it just Python imports I need to double check, or also C level? Thanks! Peter
On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock <p.j.a.cock@googlemail.com>wrote:
On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
Hi All,
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
Chuck
Hi Chuck,
Could you clarify how we'd know if this is a problem in a large package? i.e. Is it just Python imports I need to double check, or also C level?
Just Python level unless you are calling python from C. The packages are not normally imported, so you should be able to just grep through. You could also apply the patch <https://github.com/numpy/numpy/pull/3638> and see what happens. That might be the best test. Chuck
On Mon, Sep 23, 2013 at 3:18 PM, Charles R Harris <charlesr.harris@gmail.com
wrote:
On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock <p.j.a.cock@googlemail.com>wrote:
On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
Hi All,
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
Chuck
Hi Chuck,
Could you clarify how we'd know if this is a problem in a large package? i.e. Is it just Python imports I need to double check, or also C level?
Just Python level unless you are calling python from C. The packages are not normally imported, so you should be able to just grep through. You could also apply the patch <https://github.com/numpy/numpy/pull/3638> and see what happens. That might be the best test.
Also, the 1.8 release, when it comes, should issue a ModuleDeprecationWarning warning when the packages are imported. Chuck
On Mon, Sep 23, 2013 at 3:18 PM, Charles R Harris <charlesr.harris@gmail.com
wrote:
On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock <p.j.a.cock@googlemail.com>wrote:
On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
Hi All,
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
Chuck
Hi Chuck,
Could you clarify how we'd know if this is a problem in a large package? i.e. Is it just Python imports I need to double check, or also C level?
Just Python level unless you are calling python from C. The packages are not normally imported, so you should be able to just grep through. You could also apply the patch <https://github.com/numpy/numpy/pull/3638> and see what happens. That might be the best test.
I take that back. There is a _capi.c and include files for numarray. Chuck
On Mon, Sep 23, 2013 at 10:53 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Mon, Sep 23, 2013 at 3:18 PM, Charles R Harris wrote:
On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock wrote:
Hi Chuck,
Could you clarify how we'd know if this is a problem in a large package? i.e. Is it just Python imports I need to double check, or also C level?
Just Python level unless you are calling python from C. The packages are not normally imported, so you should be able to just grep through. You could also apply the patch and see what happens. That might be the best test.
I take that back. There is a _capi.c and include files for numarray.
Chuck
Thanks - I just ran our test suite against numpy compiled from that commit: https://github.com/numpy/numpy/pull/3638 We seem to be OK, so I have no objection to removing this. Peter
On 23 September 2013 18:03, Charles R Harris <charlesr.harris@gmail.com>wrote:
I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never...
I know I always like to get feedback either way ... so +1 for removal. Thanks.
participants (5)
-
Charles R Harris -
Derek Homeier -
Perry Greenfield -
Peter Cock -
Richard Hattersley