Well recur works a treat!
However.... I have one remaining problem.
On cherrypy server startup, I call a function that creates a
custom
recur.Worker object and calls its .motivate() method. A new
thread is
spawned and the worker does its thing when required.
I had assumed that when I kill the cherrypy server, all
threads spawned
by it would be killed as well. This is not the case. So, I
added a
function that should call the .stop() function of my worker
object.
Is this enough to kill the thread? Currently, when I kill
cherrypy at
the command line with cmd-C, I am not returned to a shell
prompt as a
thread is still running.
I'd appreciate any help!
Rob C
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users googlegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---
|