Unfortunately, running Futures cannot be cancelled. I believe the core reason is to ensure the same API over different implementations (it’s not possible to interrupt running threads or coroutines). The Pebble library was designed to overcome this and other limitations. from pebble import ProcessPool def function(foo, bar=0): return foo + bar with ProcessPool() as pool: … Read more
If you are truly compute bound, using the multiprocessing module is probably the lightest weight solution (in terms of both memory consumption and implementation difficulty.) If you are I/O bound, using the threading module will usually give you good results. Make sure that you use thread safe storage (like the Queue) to hand data to … Read more
This is probably bug 6721. The problem is common in any situation where you have locks, threads and forks. If thread 1 had a lock while thread 2 calls fork, in the forked process, there will only be thread 2 and the lock will be held forever. In your case, that is logging.StreamHandler.lock. A fix … Read more