FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

[Doc]: Information about deprecated colormaps missing from recent versions of the documentation · Issue #30796 · matplotlib/matplotlib · GitHub

Repository navigation

[Doc]: Information about deprecated colormaps missing from recent versions of the documentation #30796

Closed

Description

Documentation Link

https://matplotlib.org/devdocs/users/explain/colors/colormaps.html
https://matplotlib.org/devdocs/gallery/color/colormap_reference.html

Problem

Previous versions of the pyplot documentation (pre-3.5) included a list of all the available colormaps, with descriptions, and notably included the information that gist_gray, gist_yarg and binary are deprecated, and are identical to gray or gray_r.

This information was generated from a docstring that was removed in this pull request, where it was concluded that it was unnecessary to keep it because the same information is covered elsewhere. However, as far as I can see, the information about the deprecation / redundancy of these colormaps is nowhere to be found in the modern documentation.

I ran into this issue because I work on scientific software that provides colormaps and uses matplotlib's selection as a reference -- we probably don't want to include colormaps that are just duplicates. I was sure that I saw the information about these three colormaps somewhere, and fell down a rabbithole trying to figure out when and why it was removed and whether it was still accurate.

Suggested improvement

Restore the information about the deprecated colormaps somewhere in the docs, either in the tutorial or in the reference.

Activity

  1. tacaswell commented on Nov 30, 2025

    Member

    The wording is :

    The following colormaps are redundant and may be removed in future versions. It's recommended to use the names in the descriptions instead, which produce identical output:

    Which I would not say is deprecated, just "discouraged". On quick consideration, I am against fully deprecating them (setting a date to remove them and actually removing them). It has the risk of significant user disruption (old code that uses the disfavored names that is now broken and needs to be updated) for a minimal gain.

    That said, I am 👍🏻 on adding a note that says "there are identical, prefer this one".

  2. added 3 commits that reference this issue on Dec 7, 2025
    7fa8e9a
    948295a
    5ff6b1c
  3. added this to the v3.11.0 milestone on Dec 7, 2025
  4. added a commit that references this issue on Dec 11, 2025
    5da483f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL