On Tue, May 22, 2012 at 11:14 AM, Dag Sverre Seljebotn <[email protected]> wrote: > On 05/22/2012 12:06 PM, Robert Kern wrote: >> On Tue, May 22, 2012 at 9:27 AM, Nathaniel Smith<[email protected]> wrote:
>>> So maybe we should change all our DeprecationWarnings into >>> FutureWarnings (or at least the ones that we actually plan to follow >>> through on). Thoughts? >> >> Using FutureWarning for deprecated functions (i.e. functions that will >> disappear in future releases) is an abuse of the semantics. >> FutureWarning is for things like the numpy.histogram() changes from a >> few years ago: changes in default arguments that will change the >> semantics of a given function call. Some of our DeprecationWarnings >> possibly should be FutureWarnings, but most shouldn't I don't think. > > I guess the diagonal() change would at least be a FutureWarning then? > (When you write to the result?) Sure. -- Robert Kern _______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
