Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Rename cm.py to colormaps.py.#11413
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
This is the minimal version; actually changing all of the imports from |
There 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.
The colormaps module has to be added to the docs.
lib/matplotlib/cm.py Outdated
@@ -1,389 +1,5 @@ | |||
""" | |||
Builtin colormaps, colormap handling utilities, and the`ScalarMappable` mixin. | |||
This is a compatibility shim for therenamed colormaps module. |
There 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.
Link to the colormaps module
Currently the In total I'm a bit sceptical about replacing one confusion ("What does If truely rearanging stuff for the better, one would rather move the colormaps and normalizations out of |
I just saw thatMEP21 says about
|
There 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.
This re-org makes sense to me, and I think the new name is sensible.
Moving other classes around may be desirable as well, but thats a longer process.
timhoffm commentedJun 12, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I propose to hold this up until after the 3.0 release. If we are not absolutely sure this is the the right name, or if we want to do additional changes, that should be within one release. It would be really unfortunate to move stuff tocolormaps in 3.0 and then tomappables in 3.1. Also saying, we‘ve cleaned up our package structure: Here is what it looks like. Is easier to sell than having a bunch of releases saying class X is now in package Y. |
Big 👎 on "mappables" 😉. That'd be far worse than "cm" in my opinion! |
There 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.
👍 with a rebase
There 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.
Marking as 'request changes' as I want to have a careful think about this before it gets merged.
May make sense to (if we can to it with out circular imports) move color map and norm classes from colors intocolormaps.py
as well.
We should either do the whole big move for 3.0 or push the whole thing off to 3.1.
After a bit more thought I think pushing this to 3.1 so we can do the bigger re-organization, change all the examples, etc is the right thing to do. |
Because of the change of the milestone proposed by@tacaswell, I've removed the release critical tag from this PR. If this is not correct and if the PR should be still considered as release critical, please add the tag back. |
Re milestoning, but if we want to do this, we should try and actually do it 😉 |
Support has evaporated... |
We discussed this on the call and agreed that this will probably cause more trouble that it was worth. |
Closes#1476.
PR Summary
PR Checklist