[PyKDE] Exceptions and event loop (was: Web article on wxWindows and PyQt)

2003-10-05 Thread Sundance
I heard Hans-Peter Jansen said: > You could redirect stdout/stderr to an internal tee, which would > trigger a PYSIGNAL, which in turn triggers a corresponding dialog. I would *really* not want to go that way, if at all possible... I mean, having to parse a traceback for information, when an exc

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-05 Thread Hans-Peter Jansen
On Sunday 05 October 2003 16:20, Sundance wrote: > I heard Hans-Peter Jansen said: > > Erm... I happen to have another question... Exception handling > while constructing the interface works fine, but I've got a problem > with the event loop. While it is running, it'll drop all the > exceptions sil

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-05 Thread Sundance
I heard Hans-Peter Jansen said: > Just close()ing the main widget should do the job nicely, as long as > the exception doesn't occur in the ctor/dtor paths of the main > widget. Okay, danke schon! Erm... I happen to have another question... Exception handling while constructing the interface wo

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-05 Thread Hans-Peter Jansen
Hi Sundance, On Sunday 05 October 2003 04:43, Sundance wrote: > I heard Hans-Peter Jansen said: > > Conclusion: beware from using qApp.quit(), or even sys.exit(0) > > without thinking twice. There are almost always better ways to > > close a PyQt application. Use them. > > This interests me. I've