Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
MNT: make orphaned colorbar deprecate versus raise#24088
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
4ed5aa5
to06ecfd4
CompareThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Probably should fix the typo in the commit message if you make this change also.
Uh oh!
There was an error while loading.Please reload this page.
06ecfd4
to7fb75e0
CompareDo we need to add or update an API change note? I'm going to go ahead and merge this to move things along and we can follow up with another PR if we need to update docs. |
Yes, good question - I don't think we should change the existing API note, but maybe need a new one? |
…088-on-v3.6.xBackport PR#24088 on branch v3.6.x (MNT: make orphaned colorbar deprecate versus raise)
PR Summary
Closes#23973 where we, without warning, started raising if a colorbar's mappable had no axes. This adds a deprecation, and otherwise restores the previous behaviour.
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).