Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-27 Thread Dag Sverre Seljebotn
On 05/18/2012 01:48 PM, mark florisson wrote: > On 17 May 2012 23:53, Dag Sverre Seljebotn wrote: >> I'm repeating myself a bit, but my previous thread of this ended up >> being about something else, and also since then I've been on an >> expedition to the hostile waters of python-dev. >> >> I'm c

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-22 Thread Frédéric Bastien
Hi, The example with numpy array for small array, the speed problem is probably because NumPy have not been speed optimized for low overhead. For example, each c function should check first if the input is a NumPy array, if not jump to a function to make one. For example, currently in the c functi

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-18 Thread Robert Kern
On Fri, May 18, 2012 at 6:59 PM, Dag Sverre Seljebotn wrote: > On 05/18/2012 05:00 PM, Henry Gomersall wrote: >> On Fri, 2012-05-18 at 14:45 +0200, Dag Sverre Seljebotn wrote: >>> I would focus on the 'polymorphic C API' spin. PyObject_GetItem is >>> polymorphic, but there is no standard way for 3

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-18 Thread Dag Sverre Seljebotn
On 05/18/2012 05:00 PM, Henry Gomersall wrote: > On Fri, 2012-05-18 at 14:45 +0200, Dag Sverre Seljebotn wrote: >> I would focus on the 'polymorphic C API' spin. PyObject_GetItem is >> polymorphic, but there is no standard way for 3rd party libraries to >> make such functions. >> >> So let's find a

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-18 Thread Henry Gomersall
On Fri, 2012-05-18 at 14:45 +0200, Dag Sverre Seljebotn wrote: > I would focus on the 'polymorphic C API' spin. PyObject_GetItem is > polymorphic, but there is no standard way for 3rd party libraries to > make such functions. > > So let's find a C API that's NOT about arrays at all and show how so

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-18 Thread Dag Sverre Seljebotn
Henry Gomersall wrote: >On Fri, 2012-05-18 at 12:48 +0100, mark florisson wrote: >> If we can find even more examples, preferably outside of the >> scientific community, where related projects face a similar >situation, >> it may help people understand that this is not "a Numpy problem". > >Bu

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-18 Thread Henry Gomersall
On Fri, 2012-05-18 at 12:48 +0100, mark florisson wrote: > If we can find even more examples, preferably outside of the > scientific community, where related projects face a similar situation, > it may help people understand that this is not "a Numpy problem". Buffer Objects in OpenGL? _

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-18 Thread mark florisson
On 17 May 2012 23:53, Dag Sverre Seljebotn wrote: > I'm repeating myself a bit, but my previous thread of this ended up > being about something else, and also since then I've been on an > expedition to the hostile waters of python-dev. > > I'm crazy enough to believe that I'm proposing a technical

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-17 Thread Dag Sverre Seljebotn
Dag Sverre Seljebotn wrote: >I'm repeating myself a bit, but my previous thread of this ended up >being about something else, and also since then I've been on an >expedition to the hostile waters of python-dev. > >I'm crazy enough to believe that I'm proposing a technical solution to >allevi

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-17 Thread Dag Sverre Seljebotn
Dag Sverre Seljebotn wrote: >I'm repeating myself a bit, but my previous thread of this ended up >being about something else, and also since then I've been on an >expedition to the hostile waters of python-dev. > >I'm crazy enough to believe that I'm proposing a technical solution to >allevi

[Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

2012-05-17 Thread Dag Sverre Seljebotn
I'm repeating myself a bit, but my previous thread of this ended up being about something else, and also since then I've been on an expedition to the hostile waters of python-dev. I'm crazy enough to believe that I'm proposing a technical solution to alleviate the problems we've faced as a comm