[Numpy-discussion] un-silencing Numpy's deprecation warnings

Robert Kern robert.kern at gmail.com
Tue May 22 06:39:44 EDT 2012

On Tue, May 22, 2012 at 11:14 AM, Dag Sverre Seljebotn
<d.s.seljebotn at astro.uio.no> wrote:
> On 05/22/2012 12:06 PM, Robert Kern wrote:
>> On Tue, May 22, 2012 at 9:27 AM, Nathaniel Smith<njs at pobox.com>  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?)


Robert Kern

More information about the NumPy-Discussion mailing list