[Numpy-discussion] Release blockers for 1.4.0 ?

Robert Kern robert.kern@gmail....
Tue Dec 8 10:21:46 CST 2009


On Tue, Dec 8, 2009 at 10:12, David Cournapeau <cournape@gmail.com> wrote:
> On Wed, Dec 9, 2009 at 12:57 AM, Pauli Virtanen <pav@iki.fi> wrote:
>
>>
>> Also, some code that worked OK before would now start to spit out extra
>> warnings, which is not so nice.
>
> Hm, there are several things mixed up in this discussion, I feel like
> we are not talking about exactly the same thing:
>  - I am talking about setting the default back as before, which was
> warn and not print AFAIK. This means that things like np.log(0) will
> "raise" a proper warning, which can be filtered globally if wanted.
> Same for np.array([1]) / 0, etc... no stderr is involved AFAICS for
> simple examples
>  - Because warns are involved, they will only appear once per
> exception type and origin

The default has always been "print", not "warn" (except for underflow,
which was "ignore"). However, "warn" is better for the reasons you
state (except for underflow, which should remain "ignore").

-- 
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