0.6.3
Numbagg will now compile withmode="cpu"
if it detects that it's being run in a ThreadPoolExecutor
. Previously, the default mode="parallel"
could cause numba to abort the python program within that context.
Note that running in a multi-process context retains mode="parallel"
, so the new behavior should only be slower in infrequent cases, such as a local dask multi-threaded executor.
I'm not completely confident this is the globally optimal solution, so this may evolve. numba/numba#9288 has more context.