On Donnerstag, 23. August 2007, Juergen Urner wrote: > ΑΝΤΩΝΗΣ ΜΠΟΥΝΤΟΥΒΑΣ wrote: > > Yes, i got this message too but it gives absolutely no info about what > > went wrong. Imagine to have a very complex project to terminate with this > > message... > > Just wanted to give an additioal hint. Just a guess... Detlev is > currently on > summer vacation, that's why he is not responding. I stopped wading through > the depths of the debugger at a variable named qSock... and gave up. > > Jürgen > > > > > _______________________________________________ > Eric mailing list > [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/eric
Jürgen was right. I just returned from summe rvacation. The problem observed seems to be within Qt. It writes some stuff to the console. Unfortunatrely this doesn't get redirected by Python. If it did, it would show up in the shell window. If Qt (or PyQt) would raise an exception, that could be show as well. Unfortunately, I have no idea right now, how to overcome this situation. Detlev -- Detlev Offenbach [EMAIL PROTECTED] _______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
