[Numpy-discussion] 1.2 tasks

[David Huard]

On Tue, Aug 5, 2008 at 1:18 PM, Jarrod Millman <millman at berkeley.edu> wrote:

> On Tue, Aug 5, 2008 at 8:48 AM, David Huard <david.huard at gmail.com> 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 handling. The main
> > changes concern
> > 1. the definition of the bin edges,
> >     now including the rightmost edge, and
> > 2. the handling of upper outliers,
> >     now ignored rather than tallied in the rightmost bin.
> >
> > Please read the docstring for more information.
> >
> >
> >
> > If new=None  (default)
> >
> > The semantics of histogram has been modified in
> > the current release to fix long-standing issues with
> > outliers handling. The main changes concern
> > 1. the definition of the bin edges,
> >    now including the rightmost edge, and
> > 2. the handling of upper outliers, now ignored rather
> >    than tallied in the rightmost bin.
> > The previous behaviour is still accessible using
> > `new=False`, but is scheduled to be deprecated in the
> > next release (1.3).
> >
> > *This warning will not printed in the 1.3 release.*
> >
> > Please read the docstring for more information.
>
> Thanks for taking care of this.  I thought that we were going to
> remove the new parameter in the 1.3 release.  Is that still the plan?
> If so, shouldn't the warning state "will be removed in the next minor
> release (1.3)" rather than "is scheduled to be deprecated in the next
> release (1.3)"?  In my mind the old behavior is deprecated in this
> release (1.2).
>

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 old behavior and remove the new keyword.

It's pretty much the roadmap exposed in the related ticket that I wrote
following discussions on the ML.

This leaves plenty of time for people to make their changes, and my guess
is that a lot of people will appreciate this, given that you were asked to
delay
the changes to histogram.


> The 1.2 release will be longer lived (~6 months) than the 1.1 release
> and I anticipate several bugfix releases (1.2.1, 1.2.2, 1.2.3, etc).
> So I think it is reasonable to just remove the old behavior in the 1.3
> release.


> --
> Jarrod Millman
> Computational Infrastructure for Research Labs
> 10 Giannini Hall, UC Berkeley
> phone: 510.643.4014
> http://cirl.berkeley.edu/
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion at scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20080805/a2afd9d3/attachment.html>