[Numpy-discussion] Release blockers for 1.4.0 ?

Robert Kern robert.kern@gmail....
Tue Dec 8 11:54:14 CST 2009


On Tue, Dec 8, 2009 at 11:41, David Cournapeau <cournape@gmail.com> wrote:
> On Wed, Dec 9, 2009 at 1:21 AM, Robert Kern <robert.kern@gmail.com> wrote:
>
>> The default has always been "print", not "warn" (except for underflow,
>> which was "ignore").
>
> Ah, ok, that explains part of the misunderstanding, sorry for the confusion.
>
>> However, "warn" is better for the reasons you
>> state (except for underflow, which should remain "ignore").
>
> do you have an opinion on whether we should keep the current behavior
> vs replacing with warn for everything but underflow for 1.4.x ?

As far as I can tell, the faulty global seterr() has been in place
since 1.1.0, so fixing it at all should be considered a feature
change. It's not likely to actually *break* things except for doctests
and documentation. I think I fall in with Chuck in suggesting that it
should be changed in 1.5.0. I would add that it would be okay to use
the preferable "warn" option instead of "print" at that time since it
really isn't a "fix" anymore, just a new feature.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
  -- Umberto Eco


More information about the NumPy-Discussion mailing list