8000 MNT: unify code path of set, update, setp by tacaswell · Pull Request #5599 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

MNT: unify code path of set, update, setp #5599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Dec 14, 2015
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
DOC: more minor API constraints
  • Loading branch information
tacaswell committed Dec 1, 2015
commit c458cbc5321abb90f384a9cb3f7f177f5c11a419
6 changes: 6 additions & 0 deletions doc/api/api_changes/2015-12-01-TAC.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,3 +10,9 @@ The behavior of `matplotlib.Artist.update` is slightly changed to now
sort by key name and returns a list of the returned values from the
setter methods to avoid changing the API of
`matplotlib.Artist.set` and `matplotlib.artist.setp`.

The keys passed into `matplotlib.Artist.update` are now converted to
all lower case before being processed, to match the behavior of
`matplotlib.Artist.set` and `matplotlib.artist.setp`. This should not
break any user code because there are no set methods with capitals in
the names, however going forward this puts a constraint naming properties.
0