Handle dask-worker command args and extra kwargs as a list - #160
Conversation
|
Just a comment that is beyond the scope of this PR: Keeping track of all the CLI args to dask-worker in a |
|
@willirath this would probably be cleaner yes, but should we change the |
My personal feeling says: Yes, passing CLI args as a sequence is standard any way. But I'm not sure if that's representative. |
|
Okay, so I chose to follow your suggestion @willirath. |
extra kwargs as a list
|
Travis was also having a difficult monday apprently. |
|
@willirath, since you've made the comment about using a list of args, a review would be welcome! |
willirath
left a comment
There was a problem hiding this comment.
I think, the default config also has to be adapted:
dask-jobqueue/dask_jobqueue/jobqueue.yaml
Line 18 in 14c22b3
There was a problem hiding this comment.
And the interface is stil set as a string:
dask-jobqueue/dask_jobqueue/core.py
Line 204 in 14c22b3
This should be
extra += [' --interface', interface]Edit: Typo in second list item.
|
Few, thanks for that @willirath, no real testing from my part before your comments... Glad you saw those mistakes. |
|
Thanks @willirath, feel free to take a look at other PR/issues if you find the time. It could be nice to have another core maintainer. |
Sounds good. I'm not sure I'll have much time for continuous work. But it sure looks like dask clusters and dask-jobqueue will play a increasingly role in my and my group's routine work. So count me in! |
|
Nice ! We're all on the same situation about time 🙂 ! |
Fixes #156