Philipp Rudiger
Philipp Rudiger
The explicit thing to do is to respect what the user provided, if they passed in geopandas we should keep in geopandas.
Appreciate the detailed bug report. As an open source project we cannot guarantee any specific turnaround time on issue triaging although I try my best. This is definitely the right...
Okay, the fix for now is to add these imports to the flask app so that these models can be resolved: ```python import panel import panel.models.browser ``` There's two fixes...
After a brief attempt at simply attaching a callback to the node source in GraphPlot it seems like this will need a change in bokeh, since it does not seem...
This is a HoloViews issue I believe so transferring there.
Sorry to bug you guys but any timeline on getting a new release with the fix out?
Strong +1, we'll be working on migrating away from param.version and pyct for all of our projects but can't promise a timeline.
The best you'll be able to do in VSCode is using the `jupyter_bokeh.widgets.BokehModel`. This will wrap your bokeh component in an `ipywidget` which will allow bi-directional communication to work. This...
There is simply no way to access the regular Jupyter comms from inside a VSCode notebook so piggybacking on the ipywidgets comm layer is the only thing that can be...
A hard dependency in Bokeh itself? I would be okay with saying that we deprecate `push_notebook` and direct people exclusively to the `jupyter_bokeh` package and the `BokehWidget` wrapper but that...