Python executable from config file #623
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there!
I encountered the same issue as #517, also for a similar (the same?) use case.
I am running Dask Jobqueue on a SLURM system where all Python applications have to run inside (Apptainer) containers. Thus, I would like to be able to configure Dask jobqueue to use a containerized Python executable.
Currently, I can specify a custom Python path using the Dask Jobqueue Python API, but I cannot do it via the config file. It would be nice to allow for such feature, especially for users who use the Jupyter dask-lab extension, which relies uniquely on the values from the config files.
Introducing the changes as in this PR allows me to set the following in the Dask config file, so that all workers spawned by the cluster run inside containers: