Re: [Numpy-discussion] Handling of backward compatibility

2006-08-02 Thread Alan G Isaac
On Wed, 02 Aug 2006, Sebastian Haase apparently wrote: > Recently someone (Torgil Svensson) here suggested to unify > the default argument between a method and a function > - I think the discussion was about numpy.var and it's > "axis" argument. I would be a clear +1 on unifying these > and

Re: [Numpy-discussion] Handling of backward compatibility

2006-08-02 Thread Sebastian Haase
Travis Oliphant wrote: > Torgil Svensson wrote: > >>> They are supposed to have different defaults because the functional >>> forms are largely for backward compatibility where axis=0 was the default. >>> >>> -Travis >>> >>> >> Isn't backwards compatibility what "oldnumeric" is for? >> >> >>

Re: [Numpy-discussion] Handling of backward compatibility

2006-08-02 Thread Torgil Svensson
> What do people think? Is it worth it? This could be a coding-sprint > effort at SciPy. > > > -Travis Sounds like a good idea. This should make old code work while not imposing unneccessary restrictions on numpy due to backward compatibility. //Torgil

Re: [Numpy-discussion] Handling of backward compatibility

2006-08-02 Thread Stefan van der Walt
On Tue, Aug 01, 2006 at 06:21:49PM -0600, Travis Oliphant wrote: > I'm wondering about whether or not some additional effort should be > placed in numpy.oldnumeric so that replacing Numeric with > numpy.oldnumeric actually gives no compatibility issues (i.e. the only > thing you have to change i