should cm be renamed to colormaps? #1476
Comments
|
👍 on doing this |
|
This is still useful. In the meantime, the docs just need to make sure that any mention of colormap is accompanied by a note saying that the colormap module is indeed named |
efiring
added a commit
to efiring/matplotlib
that referenced
this issue
Jun 11, 2018
|
Too late. Not worth the disturbance. Decided in the devel meeting on 2020-04-27. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's a bit confusing to have a proper module have such a short, non-descriptive name.
Looking at code that uses it, if one were to see
from matplotlib import cm- they'd be left wondering what those two letters could possibly stand for. Then further down, they'd see it being used with a keyword argument that would shed some light, such ascmap = cm.RdBu, and they would maybe go through the steps of "oh, it's a map... probably a color map"...maybe...If the import code was written as
from matplotlib import colormaps as cm, it'd be more clear. We would retain the danglingplt.cmand have a dummymatplotlib.cmmodule which would just import everything frommatplotlib.colormaps.as a bonus, I think
plt.colormapsshould be retained, but the code and documentation for it should live inside this new colormaps module.The text was updated successfully, but these errors were encountered: