Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Open
Description
Summary
It seems to me that the general trend is thatset
takes keyword arguments, whileupdate
takes a dict. Hence,
one can do something like:
d= {'key1':'val','key2':2}obj.update(d)# orobj.set(**d)# orobj.set(key1='val',key2=2)
However, this is not fully consistent.
Proposed fix
Make this consistent, probably through some deprecation path. Especially, allset
methods seems to be OK, but someupdate
methods appears to use theset
approach, especiallySubplotParams
,GridSpec
andGridFinder
.
Is there a specific reason for this? (I take it that forGridFinder
, there is thempl_toolkits
-is-not-that-well-maintained issue.)
Then, at least Inherited.Text
only has anupdate
and not aset
.