Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread Jarrod Millman
On Tue, Aug 5, 2008 at 10:58 AM, David Huard <[EMAIL PROTECTED]> wrote: > The roadmap that I propose is the following: > > 1.1 we warn about upcoming change, (new=False) > 1.2 we make that change, (new=None) + warnings > 1.3 we deprecate the old behaviour (new=True), no warnings. > 1.4 remove the o

Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread David Huard
On Tue, Aug 5, 2008 at 1:36 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > On Tue, Aug 5, 2008 at 10:24 AM, Stéfan van der Walt <[EMAIL PROTECTED]> > wrote: > > Could you put in a check for new=True, and suppress those messages? A > > user that knows about the changes wouldn't want to see anythi

Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread David Huard
On Tue, Aug 5, 2008 at 1:18 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > On Tue, Aug 5, 2008 at 8:48 AM, David Huard <[EMAIL PROTECTED]> wrote: > > Thanks for the feedback. Here is what will be printed: > > > > If new=False > > > > The original semantics of histogram is scheduled to be > > depr

Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread Jarrod Millman
On Tue, Aug 5, 2008 at 10:24 AM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote: > Could you put in a check for new=True, and suppress those messages? A > user that knows about the changes wouldn't want to see anything. Yes, that is all ready available. Maybe the warning message for 'new=None' sh

Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread Stéfan van der Walt
2008/8/5 Jarrod Millman <[EMAIL PROTECTED]>: >> If new=None (default) Could you put in a check for new=True, and suppress those messages? A user that knows about the changes wouldn't want to see anything. Regards Stéfan ___ Numpy-discussion mailing li

Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread Jarrod Millman
On Tue, Aug 5, 2008 at 8:48 AM, David Huard <[EMAIL PROTECTED]> wrote: > Thanks for the feedback. Here is what will be printed: > > If new=False > > The original semantics of histogram is scheduled to be > deprecated in NumPy 1.3. The new semantics fixes > long-standing issues with outliers handlin

Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread David Huard
On Tue, Aug 5, 2008 at 4:04 AM, Vincent Schut <[EMAIL PROTECTED]> wrote: > David Huard wrote: > > > > > > On Mon, Aug 4, 2008 at 1:45 PM, Jarrod Millman <[EMAIL PROTECTED] > > > wrote: > > > > > > Question: Should histogram raise a warning by default (new=True) to warn >

Re: [Numpy-discussion] 1.2 tasks

2008-08-05 Thread Vincent Schut
David Huard wrote: > > > On Mon, Aug 4, 2008 at 1:45 PM, Jarrod Millman <[EMAIL PROTECTED] > > wrote: > > Question: Should histogram raise a warning by default (new=True) to warn > users that the behaviour has changed ? Or warn only if new=False to > remind that >

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Darren Dale
On Monday 04 August 2008 6:27:12 pm you wrote: > On Monday 04 August 2008 17:53:54 you wrote: > In my example, it is not > > > just that concat is stripping the units, it is returning a different > > type. > > By that, you mean that the result is not a NDQuantity ? Ah. > > As you mentioned Travis'

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Darren Dale
Hi Pierre, On Monday 04 August 2008 04:29:57 pm Pierre GM wrote: > On Monday 04 August 2008 14:16:33 Darren Dale wrote: > > Hi Jarrod, > > > > I was wondering if someone knowledgeable would please look into the > > behavior of concatenate() with subclasses of ndarray. > > Darren, > I ran into simi

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Pierre GM
On Monday 04 August 2008 14:16:33 Darren Dale wrote: > Hi Jarrod, > > I was wondering if someone knowledgeable would please look into the > behavior of concatenate() with subclasses of ndarray. Darren, I ran into similar problems when I started working on numpy.ma and scikits.timeseries, and I r

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Pierre GM
On Monday 04 August 2008 13:45:51 Jarrod Millman wrote: > Here are the remaining tasks that I am aware of that need to be done > before tagging 1.2.0b1 on the 8th. > The call signature for median needs to change from > def median(a, axis=0, out=None, overwrite_input=False): > to > def median(a

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread David Huard
On Mon, Aug 4, 2008 at 1:45 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > Here are the remaining tasks that I am aware of that need to be done > before tagging 1.2.0b1 on the 8th. > > Median > == > The call signature for median needs to change from > def median(a, axis=0, out=None, overwrit

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Darren Dale
Hi Jarrod, I was wondering if someone knowledgeable would please look into the behavior of concatenate() with subclasses of ndarray. I posted at scipy-dev some work on a subclass that handles units, and when two of these are concatenated, a regular ndarray is returned rather than another instan

[Numpy-discussion] 1.2 tasks

2008-08-04 Thread Jarrod Millman
Here are the remaining tasks that I am aware of that need to be done before tagging 1.2.0b1 on the 8th. Median == The call signature for median needs to change from def median(a, axis=0, out=None, overwrite_input=False): to def median(a, axis=None, out=None, overwrite_input=False): in both