We might consider adding an --env keyword to dask-worker that passed values down to the env= parameter of Nanny. (in the no-nanny case, this might fail).
Additionally in the case that this is used with --nprocs, (this is sort of hacky) it would be useful if this parameter would also support a list of inputs, so that people could pass in different environment variables for each of their processes.
This came up in rapidsai/dask-cuda#3 (comment)
I'm not sure how I feel about it.
We might consider adding an
--envkeyword todask-workerthat passed values down to theenv=parameter ofNanny. (in the no-nanny case, this might fail).Additionally in the case that this is used with
--nprocs, (this is sort of hacky) it would be useful if this parameter would also support a list of inputs, so that people could pass in different environment variables for each of their processes.This came up in rapidsai/dask-cuda#3 (comment)
I'm not sure how I feel about it.