-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Categorical order in hierarchical axis not respected #6452
Comments
Sounds reasonable. I think the correct place to implement this is around here: holoviews/holoviews/element/util.py Lines 147 to 164 in c227510
|
You don’t use typing so I’m going to ask for a bit more info before I try my hand at this. Does Don’t get me wrong: If it’s the latter, I understand, it’s better to be independent of pandas to support alternatives like polars, but that’d mean that the information about categories and their order has to be passed down somewhere. |
Really mostly an artifact of most of the code preceding the introduction of typing. Wish we'd change that, but that's obviously a huge lift.
We could use |
ALL software version info
(this library, plus any other relevant software, e.g. bokeh, python, notebook, OS, browser, etc should be added within the dropdown below.)
Software Version Info
Description of expected behavior and the observed behavior
When using multiple kvars, the category order is ignored:
Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
>>> df["cells"] 0 ~1M 1 ~10M 2 ~100M Name: cells, dtype: category Categories (3, string): [~1M < ~10M < ~100M]
Screenshots or screencasts of the bug in action
The text was updated successfully, but these errors were encountered: