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
{{ message }}
This repository has been archived by the owner on Oct 26, 2019. It is now read-only.
I deployed this very simple test notebook (attached as .txt because github doesn't allow .ipynb) using plotly from my jupyter notebook (using a python 3 kernel) to my jupyter dashboards server. I tried both a normal jupyter-dashboards-server installed through npm and a dev version cloned form the current HEAD of the git repos. But as soon as I open the dashboard, the firefox console gives me the following error:
ImportError : No module named 'plotly'
ImportErrorTraceback (most recent call last)
<ipython-input-1-e10b0939f114> in <module>()
1 import pandas as pd
2 import numpy as np
----> 3 import plotly.graph_objs as go
4 import plotly.figure_factory as ff
5 from plotly.offline import download_plotlyjs, init_notebook_mode, plot, iplot
The dashboard runs fine with both a python2 and python3 kernel in the regular jupyter notebook on exactly the same machine though, and plotly is installed. Why doesn't the jupyter dashboards server not see plotly? Does it use a different PYTHONPATH?
Cheers,
Dolf.
The text was updated successfully, but these errors were encountered:
I deployed this very simple test notebook (attached as .txt because github doesn't allow .ipynb) using plotly from my jupyter notebook (using a python 3 kernel) to my jupyter dashboards server. I tried both a normal jupyter-dashboards-server installed through npm and a dev version cloned form the current HEAD of the git repos. But as soon as I open the dashboard, the firefox console gives me the following error:
The dashboard runs fine with both a python2 and python3 kernel in the regular jupyter notebook on exactly the same machine though, and plotly is installed. Why doesn't the jupyter dashboards server not see plotly? Does it use a different PYTHONPATH?
Cheers,
Dolf.
The text was updated successfully, but these errors were encountered: