Replies: 1 comment 3 replies
-
@tgy Using the Bokeh server requires Tornado, which is not included in the requirements in the recipe you link above, that means that Bokeh would be limited exclusively to standalone (non-Bokeh server) capabilities. AFAIK porting Tornado to pyodide would be huge undertaking, and I have not heard of anyone claiming to be working on it, so I would not expect Bokeh server in its current form to use usable on pyodide any time soon. Some other possibilities:
|
Beta Was this translation helpful? Give feedback.
-
I see a very interesting use-case in serving an interactive bokeh plot within a static web page, with the bokeh server running in websassembly via pyodide ( https://github.com/pyodide/pyodide ).
One example of application would be to have interactive plots, with Python callbacks, within a statically-generated website (e.g. a scientific blog). Because everything would run in the web browser, even the bokeh server, this would scale much better than having to run a bokeh server answering requests for all visitors.
It seems that bokeh is supported by pyodide ( tytgatlieven/pyodide@3645814 ).
If this is already possible, maybe it would be a good idea to provide an example in the bokeh documentation.
In particular, on this page of the documentation https://docs.bokeh.org/en/latest/docs/user_guide/embed.html it says that the standalone document does not require a bokeh server to run. If this webassembly-ran bokeh server idea is possible right now using pyodide, then we can extend this definition of standalone documents because we could potentially run standalone documents that do run a bokeh server.
I'm opening the discussion here about this subject, and I'm potentially missing something, because I'm no expert in this new tech. However, my internet search did not lead to me to a conclusive answer on this subject.
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions