[Numpy-discussion] how can one catch a multiarray.error

Robert Kern robert.kern@gmail....
Tue Jun 2 21:25:10 CDT 2009


On Tue, Jun 2, 2009 at 21:20, Charles R Harris
<charlesr.harris@gmail.com> wrote:
>
>
> On Mon, Jun 1, 2009 at 8:43 PM, Robert Kern <robert.kern@gmail.com> wrote:
>>
>> On Mon, Jun 1, 2009 at 21:37,  <josef.pktd@gmail.com> wrote:
>> > how do we catch a multiarray.error in a try except clause?
>> >
>> > e.g.
>> >>>> np.argmin([])
>> > Traceback (most recent call last):
>> >  File "<pyshell#147>", line 1, in <module>
>> >    np.argmin([])
>> >  File
>> > "C:\Programs\Python25\Lib\site-packages\numpy\core\fromnumeric.py",
>> > line 631, in argmin
>> >    return _wrapit(a, 'argmin', axis)
>> >  File
>> > "C:\Programs\Python25\Lib\site-packages\numpy\core\fromnumeric.py",
>> > line 37, in _wrapit
>> >    result = getattr(asarray(obj),method)(*args, **kwds)
>> > multiarray.error: attempt to get argmax/argmin of an empty sequence
>>
>> try:
>>   ...
>> except numpy.core.multiarray.error:
>>   ...
>>
>> Unfortunately, that is still a string exception. We should change that.
>
> I'm fixing these, but doesn't that constitute an abi change? Code that used
> to catch the exceptions won't anymore.

If they are catching numpy.core.multiarray.error, then it's not a
problem. They never should have been catching "multiarray.error".

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