APScheduler already uses a thread pool to execute the callbacks. If you
have two different jobs that execute code that accesses some shared
resource, you need to handle that with explicit locking.
> Thanks,
> Braun Brelin
> --
> You received this message because you are subscribed to the Google
> Groups "APScheduler" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
apscheduler...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>