techinically any scheduler worker is a fresh process spawned with multiprocessing.Process, so spawning a thread, albeit counterproductive, is allowed. I'm not that sure that launching a process from inside a spawned process play wells with input/output buffers. In any case, using multiprocessing.Popen spawns a new thread already under the hood
On Friday, October 2, 2015 at 3:44:55 AM UTC+2, Bilal Hasan wrote: > > Before I tested this out (I'm running on production environment), I wanted > to ask would it be okay to spawn threads in the scheduler function? > > Since I need to split some tasks using the Linux command line. > > What would be the best way to do this? > > Using the threading library? Or just run a bunch of subprocess Popen calls > and not wait on those to return? > > Any help or feedback ointing me into the right direction on how to use the > scheduler with threads would be appreciated. > Thanks. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
