Unexpected kwargs error
See original GitHub issueIt appears that https://github.com/dask/distributed/pull/3117 introduced a check for whether certain kwargs were used when initializing a Client
.
Previously, this sort of pattern was allowed:
from distributed import Client
c = Client(processes=True, silence_logs=True)
with the expectation that these kwargs were passed down to the LocalCluster
object which is created when a scheduler address is not provided. Now this raises:
ValueError: Unexpected keyword arguments: ['processes', 'silence_logs']
- is this an unsupported use of the API with the release of 2.6.0?
- or should Dask only be raising these kwarg errors whenever a
scheduler_address
is actually passed?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Why am I getting this unexpected keyword argument TypeError?
When passing kwargs into a function, it expects to find the exact variable name in the list. If instead your dictionary keys were...
Read more >False positive on unexpected argument for **kwargs with ...
It seems that the * pseudo-argument in f1 triggers the problem. Seems to be related to PY-14449.
Read more >How to debug task "got an unexpected keyword argument"
1.) The part of the error message "Task tasks.product_add" looks to me like Celery thinks your product_add function is actually a task. However,...
Read more >Unexpected Keyword Argument in Python - Codeigo
The primary solution to the error is to pass the keyword arguments expected by the function/class. This can be achieved in two ways....
Read more >Error: got unexpected keyword argument when deleting object ...
Error: got unexpected keyword argument when deleting object in admin interface ... in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bryanwweber Thank you. This issue was reported already at discourse discussion
That works for me! I had forgotten that these clients were created with this utility which force-fed the kwargs when I originally opened the issue - I’ve already fixed it on my side 👍