On Feb 28, 8:56 am, Phil Thompson <[EMAIL PROTECTED]> wrote: > On Tuesday 27 February 2007 11:09 pm, shredwheat wrote: > > > When your programs stops with the error, it should also be printing a > > stack trace. This is a list of all the functions that have been called > > when Python had the problem. > > > You shouldn't have to do anything extra to get the stack trace. > > The error is raised in Qt and aborts immediately. It never gets back to Python > to generate a trace. > > He needs to produce a short and complete test which demonstrates the problem, > then we can point out where the QPaintDevice is being created. > > Phil
OK, but before I do a complete test, could anybody tell/explain me why the same file is working on Windows? Did anybody already meet with something similar Win vs. Linux? b. -- http://mail.python.org/mailman/listinfo/python-list
