-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some categorical colormaps are given as list of numerical RGB instead of list of hex strings #69
Comments
I'm not sure what
What's confusing is that for some colormaps the usual way to refer to them is through an alias like Short of making Bokeh understand the list of numeric triples, I guess our options are to apologize and point out this issue in the docs, or change the name of the native Glasbey ones to something unwieldy and then use the names like |
Sorry I meant Ok I understand the logic behind this, and it explains why on the contrary In my opinion from a user perspective an inconsistency remains, as there is a different treatment for seemingly similar objects with short names (such as |
colorcet 2.0.6
The colorcet user guide specifically mentions that it provides 'Bokeh-style' palettes as lists of hex strings, which is handy when working with Bokeh.
However, I realised this was not the case for some of the categorical palettes, including
cc.glasbey_bw
andcc.glasbey_hv
. These return lists of RGB triplets which don't work with Bokeh.Accessing these palettes by string name (e.g.
cc.palette['glasbey_hv']
) does yield a list of hex strings... so this is only an issue with regard to consistency.The text was updated successfully, but these errors were encountered: