@mwaskom I am working on this.

@mwaskom I could not find the documentation where this warning is mentioned .Please help.

This note is going to be removed for 3.6, so the documentation update would be on the 3.5.x branch. See this PR for the locations of the various pieces of code surrounding this note: #22298

References to a few other issues/PRs that this has stemmed from: #20853, #20853, #19766, #16991

The previous versions of Matplotlib would return the same object every time, which caused issues with changing a mutable state for future access of colormaps. In 3.6+ get_cmap() will return a copy of the colormap with each request. If you weren't getting warnings/errors about "modifying the global state of a colormap" within code, then there shouldn't be any updates necessary.

matplotlib.cm.get_cmap() is still available and there is now a new ColormapRegistry that lives at matplotlib.colormaps which can be used like a dictionary matplotlib.colormaps["viridis"].

@soma2000-lang Thanks for the willingness to help, but this is pretty subtle, and I think we need someone who understands those subtleties to fix the message.

Ok.