Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
using ``export_png`` or ``save`` without filename from within jupyter notebook saves png file to lib/python
See original GitHub issueUsing bokeh.io.export_png, bokeh.io.export_svg or bokeh.io.save from within a jupyter notebook without specifying an output filename causes the file to be written to lib/python (on my machine it’s ‘/Users/lcanavan/miniconda3/envs/bokeh/lib/python3.5/runpy.png’.
It’s likely due to how if there’s no filename arg, we infer the name of the script the document is in. A notebook is apparently executed by this runpy.py script in lib/python, so that’s the generated name.
Is there a consistent way to get the path of a jupyter notebook from inside the session?
Bokeh 0.12.7dev3
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Personally I am fine with making filenames required at all times.
Anyway to specify the location where export_png saves the file? either a local location or on aws?