-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Plotly Express strange hover_data ValueError #1683
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
Comments
Apologies; I figure out that you are supposed to feed columns inside a list rather than just a string of the column name like the other items. Closing out. |
Had the exact same issue. This is indeed a very misleading error message though, and very much seem to be a bug as it says It would make sense if it says something like "list of column names expected but received a single str". |
@zhaomh1998 we have an open issue #2177 to improve the error message, it should be improved soon :-). |
Please fix this. |
We haven't gotten around to it yet... Contributions are welcome :) |
just came here to say these comments helped me. :) |
The answers have helped me as well. For other newbies like myself, to pass all the columns you can do |
Scatter plotting with no problems, until I attempted to map a column of my data to hover_data.
Here's what my data looks like. I'm trying to map the
most_similar_kt
column to hover_data.Here's the error message:
ValueError: Element of value of 'hover_data' is not the name of a column in 'data_frame'. Expected one of ['x', 'y', 'label', 'freq', 'similarity', 'size', 'class', 'most_similar_kt'] but received: m
And here's my code:
fig = px.scatter(df, x='x',y='y', color='similarity', size='size', symbol='class',hover_name='label', hover_data='most_similar_kt', width=1500, height=1000, template='plotly_dark', render_mode='webgl')
Apologies if this has already been addressed; I spent 10 minutes googling for errors and it doesn't appear anyone else had this issue.
If I

remove the hover_data assignment
, then the plot works:Thanks for your assistance!
The text was updated successfully, but these errors were encountered: