Skip to content
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

Almond initialization bug #149

Open
eric-czech opened this issue Jan 2, 2020 · 0 comments
Open

Almond initialization bug #149

eric-czech opened this issue Jan 2, 2020 · 0 comments

Comments

@eric-czech
Copy link
Contributor

I found that if you start a notebook on a fresh kernel, create a plot, run the same cell again to recreate the same plot, and then refresh the page without restarting the kernel, the plot will no longer render. More importantly, this means that if you ever rerun whatever plot you created first then it won't render anywhere else (like nbviewer) even though the plots are still rendering well in the notebook/page you've created them with.

This seems to be because the call to Almond.init is happening under the scenes when the first plot is generated but then the plotly JS dependency definition is lost on a rerun of the same plot. Do you think there Is there a better way to do that? The two best solutions I can think of are to either force that call to be explicit (like plotly-python) or make sure that caveat is documented well.

Happy to work on a PR one way or the other for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant