On Nov 10, 2007 3:33 PM, Michael McNeil Forbes [EMAIL PROTECTED]
wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? I know that the behaviour can be controlled by
seterr(), but it seem rather unpythonic not to use the warnings library.
Is there an
Michael McNeil Forbes wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? I know that the behaviour can be controlled by
seterr(), but it seem rather unpythonic not to use the warnings library.
The warn option explicitly allows you to use the
On 13 Nov 2007, at 8:46 AM, Travis E. Oliphant wrote:
Michael McNeil Forbes wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? ... in util.py ...
The warn option explicitly allows you to use the warnings library.
There is already the print mode
On Nov 13, 2007 11:48 AM, Michael McNeil Forbes [EMAIL PROTECTED]
wrote:
On 13 Nov 2007, at 8:46 AM, Travis E. Oliphant wrote:
Michael McNeil Forbes wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? ... in util.py ...
The warn option
Why are numpy warnings printed rather than issued using the standard
warnings library? I know that the behaviour can be controlled by
seterr(), but it seem rather unpythonic not to use the warnings library.
Is there an explicit reason for this choice? (It seems like a pretty
trivial