You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated to seaborn 0.11 and get an error with code that did not even give a warning with seaborn 0.10.
I have a pandas DataFrame with hierarchical columns. That means that I reference a column like so:
df[('0th_order_col_name', '1st_order_col_name')]
When I try to specify such a hierarchical column label in, for instance, a scatterplot, seaborn now gives me an error because it tries to interpret this hierarchical column label as data.
Hierarchical columns add a lot of complexity. They're not "tidy", strictly speaking. My inclination would be to say that they're not supported, because it was never claimed that they were. But it does look like they worked, accidentally, in more places than I realized. So I can look into how disruptive it would be to handle them in the refactored code.
I updated to seaborn 0.11 and get an error with code that did not even give a warning with seaborn 0.10.
I have a pandas DataFrame with hierarchical columns. That means that I reference a column like so:
df[('0th_order_col_name', '1st_order_col_name')]
When I try to specify such a hierarchical column label in, for instance, a scatterplot, seaborn now gives me an error because it tries to interpret this hierarchical column label as data.
The error message is
The change was introduced in #2205
The text was updated successfully, but these errors were encountered: