Agree w the general idea of this change because when I wrote the tutorial I didn’t understand that listed colormap behave differently. From list looks pretty useful. My main concern w this tutorial was to show how to paste existing colormaps together or make new ones from rgb arrays. If from list is a better way to do that than listed colormaps maybe modify or add new examples?

I'm not sure if any more examples are needed, but of course feel free to suggest something. The main benefit of LinearSegmentedColormap.from_list(list) compared to LinearSegmentedColormap(dict) is just the reduced number of headaches for beginners creating that dictionary. But both aren't in competition with ListedColormap, I'd say.

Thanks, this clarifies quite a few things...

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout v3.1.x
$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 1f003b0504ae71c0bdf47c6c1dc644d39e39dcc5

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #14968: DOC: colormap manipulation tutorial update'

4. Push to a named branch :

git push YOURFORK v3.1.x:auto-backport-of-pr-14968-on-v3.1.x

5. Create a PR against branch v3.1.x, I would have named this PR:

"Backport PR #14968 on branch v3.1.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to suggest an improvement.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout v3.1.1-doc
$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 1f003b0504ae71c0bdf47c6c1dc644d39e39dcc5

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #14968: DOC: colormap manipulation tutorial update'

4. Push to a named branch :

git push YOURFORK v3.1.1-doc:auto-backport-of-pr-14968-on-v3.1.1-doc

5. Create a PR against branch v3.1.1-doc, I would have named this PR:

"Backport PR #14968 on branch v3.1.1-doc"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to suggest an improvement.

This is helpful, but I don't think critical to back port unless you want to do it @ImportanceOfBeingErnest ?

No, I guess we can leave it like this.