Some weeks ago there was a post on this list requesting feedback
on possible future directions for numpy. As I was quite busy at that
time I'll reply to it now.
My POV is that of a novice user, who at the same time wants quite
badly to use the numpy framework for his numerical work which in
this c
On Thu, Jul 16, 2009 at 12:27:03PM -0400, Ian Stokes-Rees wrote:
> But keep in mind there are costs to running the event, and an associated
> registration fee. It seems only fair that any webcasting or recording
> only be made available at some cost to the viewers. I would be happy to
> pay t
On Thu, Jul 09, 2009 at 12:00:23PM -0500, Robert Kern wrote:
> On Thu, Jul 9, 2009 at 11:44, Fons Adriaensen wrote:
>
> > There is a simple rule which says that if you use an object
> > pointer as a function argument you must INCREF it. This is
> > just the logical consequ
On Thu, Jul 09, 2009 at 04:30:11PM +0100, Citi, Luca wrote:
> Also one could have an internal flag which says whether or not is safe
> to overwrite inputs with ref_count=1.
> Then import_array() sets this flag to "unsafe" (i.e. current behaviour).
> If the user of the numpy C-api is aware of how t
Hello all,
(resending for the Nth time, as the previous attempts
didn't make it to the list)
I'm new to this list (and numpy is mostly new to me :-).
Using python 2.6 and numpy 1.3.
My plan is to write some C extensions that will perform
rather specialised processing on multichannel digital au
On Wed, Jul 08, 2009 at 11:01:55PM +0100, Peter wrote:
> On Wed, Jul 8, 2009 at 10:00 PM, Fons Adriaensen wrote:
> >
> > On Sun, Jul 05, 2009 at 12:22:37AM +0200, Stéfan van der Walt wrote:
> >
> >> 2009/7/5 Pauli Virtanen :
> >> > 2009-07-04 22:52 +
On Sun, Jul 05, 2009 at 12:22:37AM +0200, Stéfan van der Walt wrote:
> 2009/7/5 Pauli Virtanen :
> > 2009-07-04 22:52 +0200, Fons Adriaensen wrote:
> > [clip]
> >> I subscribed to numpy-discussion almost two days ago.
> >> I do receive messages from the lis
