mypy issues as of 2.8.0 about libcloud HOT 3 CLOSED

@dpeschman Thanks for reporting this issue, we will have a look.

As far as adding **kwargs goes - I don't think it should be part of the standard API. The whole point behind the standard API is so you know up front which arguments are available and supported.

Drivers can still use it, but even there explicitly declaring supported arguments is preferred and there are usually very few valid cases for using **kwargs (recent improvements related to that - #1389).

EDIT: On a related noted - do you have a specific / valid use case for **kwargs in mind?

from libcloud.

Forgot one more - what do you think about adding **kwargs back to create_node?

from libcloud.

Our use case is that our custom drivers take additional/other parameters to create_node that aren't in the base API. But I see your point about using explicit keyword args and will update our drivers to do that and continue to ignore the mypy/lint arg mismatch in this case.

from libcloud.