Re: [matplotlib-devel] Interrupt is fixed

[Neal B. <ndb...@gm...>]

I'm afraid it's only an annoyance, and I doubt I'll be motivate to try to hunt 
that down.

Benjamin Root wrote:

> On Wed, Jul 18, 2012 at 1:40 PM, Neal Becker
> <ndb...@gm...> wrote:
> 
>> OK, my mistake.  I'm using 1.1.1rc2.
>>
>> I was using a new installation without any matplotlibrc, and was defaulted
>> to
>> gtk.
>>
>> If I set:
>> backend : Qt4Agg
>>
>> then the problem has returned.
>>
>>
> Usually, the source of such problems is someone using a bare try...except.
> KeyboardInterrupt subclasses BaseException.  There is a subtle difference
> between
> 
> try:
>    foo()
> except:
>    pass
> 
> and
> 
> try:
>     foo()
> except Exception:
>     pass
> 
> The first will capture Ctrl-C and throw it away, while the latter will
> not.  PEP8 recommends against blind usage of bare except clauses.
> 
> Happy hunting!
> Ben Root