On Tuesday 10 December 2002 10:47 am, David Abrahams wrote:
> Phil Thompson <[EMAIL PROTECTED]> writes:
> > Another possible conflict, perhaps more likely, is the two modules
> > fighting over the Qt API.
>
> Could you be a little more specific about what this might mean?

Not really - just an uncomfortable feeling about events being dispatched from 
an object wrapped by one module to an object wrapped by another module that 
calls a virtual re-implemented in the first module etc, etc.

BTW, dclock.py doesn't use threads explicitly, but any SIP generated code will 
cooperate with the Python thread infrastructure and the GIL.

Phil

_______________________________________________
PyKDE mailing list    [EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde

Reply via email to