Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/10/07, Robert Kern <[EMAIL PROTECTED]> wrote: Charles R Harris wrote: > Is there a reason that the pointer PyArray_API remains valid if the > imported numpy module is garbage collected? Or is the imported module > persistent even though the returned object goes away? I assume that > python

Re: [Numpy-discussion] Exported symbols and code reorganization.

Charles R Harris wrote: > Is there a reason that the pointer PyArray_API remains valid if the > imported numpy module is garbage collected? Or is the imported module > persistent even though the returned object goes away? I assume that > python did a dlopen somewhere. There is no provision in Pyt

Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On Jan 10, 2007, at 13:52 , Charles R Harris wrote: > On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On > Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > > > That brings up the main question I have about how to break up the C > > f

Re: [Numpy-discussion] Exported symbols and code reorganization.

On Jan 10, 2007, at 13:52 , Charles R Harris wrote: > On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On > Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > > > That brings up the main question I have about how to break up the C > > files. I note that most of the functions in multiarraymo

Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > That brings up the main question I have about how to break up the C > files. I note that most of the functions in multiarraymodule.c, for > instance, are part of the C-API, and are tagged

Re: [Numpy-discussion] Exported symbols and code reorganization.

On Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > That brings up the main question I have about how to break up the C > files. I note that most of the functions in multiarraymodule.c, for > instance, are part of the C-API, and are tagged as belonging to > either the MULTIARRAY_API or the

Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/9/07, David Cournapeau <[EMAIL PROTECTED]> wrote: Charles R Harris wrote: > > > On 1/7/07, *Robert Kern* <[EMAIL PROTECTED] > > wrote: > > Charles R Harris wrote: > > > > > No, but as with mtrand, most of those arise from the fact that > these function

Re: [Numpy-discussion] Exported symbols and code reorganization.

Charles R Harris wrote: > > > On 1/7/07, *Robert Kern* <[EMAIL PROTECTED] > > wrote: > > Charles R Harris wrote: > > > > > No, but as with mtrand, most of those arise from the fact that > these functions > are implemented in files other than the C file th

Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/7/07, Robert Kern <[EMAIL PROTECTED]> wrote: Charles R Harris wrote: No, but as with mtrand, most of those arise from the fact that these functions are implemented in files other than the C file that contains the Python module code. In order for them to be called from the Python modul

Re: [Numpy-discussion] Exported symbols and code reorganization.

Charles R Harris wrote: > Hi all, > > I've started some experiments at breaking up the large > multiarraymodule.c and arrayobject.c files. As part of this I also > looked at what symbols are currently exported by the *.so libraries. > Most are just the usual three python symbols, but multiarray,

[Numpy-discussion] Exported symbols and code reorganization.

Hi all, I've started some experiments at breaking up the large multiarraymodule.cand arrayobject.c files. As part of this I also looked at what symbols are currently exported by the *.so libraries. Most are just the usual three python symbols, but multiarray, mtrand, and fftpack_lite have extras