you're translating my "like" as in "exactly". and making assumptions, wrong ones.
I just said that the environment in which the scheduler executes your task is LIKE a shell one, where you launch the FUNCTION you queued, and then exit the shell. At the very "raw" structure of the scheduler, it just see if there are tasks ready to be processed, opens a shell env, executes the function, records the output, closes the shell. for every task. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
