Thomas Moreau

Hello, I happen to be investigating the same issue with a different config. Trying to setup `python` and `julia` both from `conda-forge` on linux. The julia version is different (v1.0...

There is a method `Future.cancel`, which can cancels jobs that were not already dispatched. Also, it is possible to shutdown the executor with `executor.shutdown(kill_workers=True, wait=True)`. Did you have something more...

> Community-wide consistency beats @tomMoral's aesthetic preferences in my opinion :) consistency with cpython seems more important than uniformization 😅

I am fine if we use the `88`. If it is the norm with `black`, let's avoid having more special cases. My main issue with this change is that it...

I can reproduce this with `loky` and the following script: ```python from loky import get_reusable_executor def import_dt(k): import datatable as dt # Create an executor with 2 worker processes executor...

The discrepancy with `concurrent.futures` is because we do not start the processes with `fork` by default. Starting the processes with fork breaks the POSIX standard and can lead to unexpected...

First of all, what is your goal in using `loky`? It is unclear and you seem to be confused on what is the purpose of `loky`. The goal of `loky`...

Hello and thanks for the kind words for `loky` :) For now, `loky` only provides a fix ordering for the task indeed. This part is mainly due to the use...

This behavior is due to the fact that `loky` uses `cloudpickle` to serialize its communications. `cloudpickle` propagate the value of the global variables from the main process to the child...

Note that this is linked to what was discussed in #206, and that if the extra module is not possible, it is possible to have similar behavior with a hackish...