-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
[Bug] HTML wont display #33
Comments
Hi @LaurenBK, |
Hi, yes please that would be great. Databricks has a method to display html but the command is slightly different to jupyter which is why the current html helper is not displaying it correctly. I should be able to get around this with the string |
Now that I think about it, maybe it would make sense to add an internal check for environment and if it's Databricks then use different display function? |
That would be much simpler for a user. Would checking for a Databricks environment be simple though? It looks like you might do it by checking for environment variables but would these always be set up the same way? It might end up being more work down the line. |
I'll think about implementing both options. Returning html as a string is simpler and it would be a good "quick and dirty" workaround but in longer perspective I'll think about adding automatic platform detection to better address running IPyPlot in different environments |
Experiencing same issue here. How can I return the HTML as string with |
Hi, thank's for this package - it looks like exactly what I was looking for.
I am struggling to find a way to use this in Databricks though which is where I want to use this. The package runs fine but instead of seeing the output as an image, I see
<IPython.core.display.HTML object>
twicewhen I try
ipyplot.plot_images
oripyplot.plot_class_tabs
Is there a way to add a flag to return the html directly from the function call so I can use the built in function to display html? Because the html is hidden, I can't click the link that would display the html
The text was updated successfully, but these errors were encountered: