while adapting cmyt to this change, I noticed thatLinearSegmentedColormap still silently accepts the parameterN, shouldn't it be deprecated too ?
(same goes forLinearSegmentedColormap.from_list)

The effect / usage ofN inLinearSegmentedColormap is different:

• ForListedColormap it only cuts or expands the given list of colors, which can easily be done by the user.
• ForLinearSegmentedColormap,N defines the internal sampling. The input are RGB curves, which may be very coarsly defined via only a few points. Because we don't want interpolate these curves for every color lookup,LinearSegementedColormap internally samples these curves into a lookup table. N controls this sampling. If we would removeN here, that means the user would have to do the sampling, and then we'd be effectively back to aListedColormap. In other words, the added benefit ofLinearSegmentedColormap is that you can specify the RGB curve on a high level, and the colormap does the sampling into a lookup table for you. That fundamentally needsN as a control parameter.

LinearSegmentedColormap.from_list is only a slightly simpler interface that limits the RGB curves to continuous curves (i.e. you cannot have discontinous jumps), it this equally needsN for the internal sampling.

Therefore, there is no plan to discardN forLinearSegmentedColormap.

thanks a lot for this detailed explanation !