Their speculation in the later part of that thread is essentially correct.
Nbconvert runs your Python code and produces the output, which from
point the Bokeh backend it needs to talk to is gone, so it can't display
to run it in a browser. Depending on your use case, that could mean
automating a headless browser (using e.g. Selenium), or some extra
On 8 August 2017 at 08:17, Güngör Budak <gngr...@gmail.com> wrote:
> I'm using bokeh to generate interactive visualizations and I want to
> pre-render / execute the notebooks I programmatically generate using
> "jupyter nbconvert --to notebook --execute notebook1.ipynb --output
> notebook1_output.ipynb". Although it seems it executes the cells but the
> outputs from JS powered visualizations are not stored in the executed
> notebook file and manual execution is required on the browser.
> Is there a way to keep such outputs in the notebook files programmatically
> through Terminal?
> We had some discussion on bokeh forums please have a look at it
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to email@example.com.
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.