|
From: John H. <jdh...@ac...> - 2004-11-22 22:50:48
|
>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:
Fernando> I realize that excepthook is a tempting tool to use, but
Fernando> I hope you guys reconsider this. I really think it
Fernando> would cause many more headaches down the road than those
Fernando> it initially appears to solve.
OK, good to know. That was news to me. Now why is it that ipython
and envisage get to mess around with it and we don't :-) ?
So what is the canonical way to funnel exceptions into GUI dialog
boxes? Isn't this what sys.except_hook is for?
Actually, it would be fine if matplotlib overrode sys.except_hook and
ipython later came along and overrode that. Basically, ipython would
be saying, "I know I've got a shell to display errors in, so we don't
need to GUI method". I don't think matplotlib would have a problem
with that. Ditto for envisage. Basically, we would be providing a
default method to get the message to the GUI which could be overriden
by other applications that want to (ipython, envisage, what-have-you).
So I don't really see a danger here, but please educate me!
JDH
|