"(*)·´`·.¸.»ÐëÄdMäñ·´`·.¸.»(*)" writes:
> I asked on #twisted and someone said that something about my
> application running as daemon and that destroys all threads spawned
> before that, and that I should spawn the thread *after* it's fully
> daemonized.
reactor.callWhenRunning() could be used t
Hi thanks for the reply,
I have a separate module that doesn't/shouldn't depend on Twisted, and
this module is begin called from a Twisted application, and it needs
to spawn a thread the thread doesn't call anything within Twisted, the
problem is when I call start() the thread doesn't run, but If
(*)·´`·.¸.»ÐëÄdMäñ·´`·.¸.»(*) wrote:
> Hi,
>
> I'm trying to spawn a threading.Thread from a Twisted application, but
> the thread won't start unless I schedule the the code with
> reactor.callLater(), any Ideas ?
Twisted doesn't affect threading.Thread at all.
You haven't given much detail, so
Hi,
I'm trying to spawn a threading.Thread from a Twisted application, but
the thread won't start unless I schedule the the code with
reactor.callLater(), any Ideas ?
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.
