Closed ceball closed 1 year ago
This will likely work when we support vanilla jupyter notebook, which is actually a very straightforward and easy things to implement it but I stopped doing it since it makes dist annoying: https://github.com/finos/perspective/pull/1063
We can reimplement a more minimal version of that PR and it should allow for non-JupyterLab context.
I believe this will work after the latest release is done https://github.com/finos/perspective/pull/2136
@timkpaine I get this message in the Output panel-
17:42:28.125 [debug] VSCodeNotebookController::handleExecution, Class name = Dy, completed in 163ms, has a falsy return value
17:42:28.171 [debug] Widget Message: WidgetManager: Loading class LayoutModel:@jupyter-widgets/base:2.0.0
17:42:28.173 [debug] Widget Message: WidgetManager: Loading class PerspectiveModel:@finos/perspective-jupyterlab:~2.2.1
17:42:28.176 [debug] Widget Message: WidgetManager: failed, Loading class PerspectiveModel:@finos/perspective-jupyterlab:~2.2.1
17:42:28.176 [error] Widget load failure {} {
className: 'PerspectiveModel',
moduleName: '@finos/perspective-jupyterlab',
moduleVersion: '~2.2.1',
cdnsUsed: false,
isOnline: true,
timedout: false,
error: '{}'
}
Support Question
When I try to use PerspectiveWidget in vscode, I get "nothing" (no display).
I'm using an environment in which PerspectiveWidget works in jupyter lab, and in which other ipywidgets work in vscode.
Notes:
Steps to Reproduce:
python -m pip install perspective-python ipywidgets jupyterlab
jupyter labextension install @jupyter-widgets/jupyterlab-manager
jupyter labextension install @finos/perspective-jupyterlab
The code I'm using to verify ipywidgets work in general:
And perspective:
Working in jupyter lab:
Not working in vscode:
Though other ipywidgets work:
I am using the same python environment in both vscode and jupyter lab. In vscode, for its "how to connect to Jupyter" option, I tried both "default" (allow vscode to start a server) and I tried specifying the same (existing/already running) jupyter server as used above.
Unfortunately I don't (yet) know how to get more details about what is going wrong in vscode.
Environment:
I have only tried one environment.