Move the repo to the `jupyterlite` organization?
Thanks again for putting this repo together!
I was wondering: since some of the development happening here is somewhat related to the efforts happening on JupyterLite: do you think the jupyterlite organization on GitHub could be a new home for the repo?
Maybe it would also be a good opportunity to add support for other kernels than Python? For example p5.js, Lua and Wren are also supported in JupyterLite:
- https://github.com/jupyterlite/p5-kernel
- https://github.com/jupyterlite/xeus-lua-kernel
- https://github.com/jupyterlite/xeus-wren-kernel
With more Xeus-based kernels on the way: https://blog.jupyter.org/xeus-lite-379e96bb199d
Probably the vscode-pyolite extension for VS Code could either be made more generic to support different kernels? For example the logic should be quite similar for Xeus-based kernels since they also run WebAssembly in a Web Worker.
Another benefit to the move would be an increased visibility for the extension so it's more discoverable.
Finally it would be great to check if it's possible to deploy a static version of VS Code (with extensions). Just like vscode.dev but self-hosted. This means folks would be able to deploy their own VS Code alongside JupyterLite with the JupyterLab and RetroLab interfaces, served via a plain HTTP server. Maybe it's already possible to do a custom static build with the latest web version of VS Code? (directly from https://github.com/microsoft/vscode)
%pip install pytest-cov hypothesis ipytest- is probably advisable given that testing hypotheses is core to the scientific method, and code coverage is a worthwhile metrics, and it's not yet possible to run a Terminal or CLI tools in JupyterLite
$ pytest notebook.ipynbwould just work if:- https://github.com/jupyterlite/jupyterlite/issues/949
- https://hypothesis.readthedocs.io/en/latest/quickstart.html#running-tests
- is probably advisable given that testing hypotheses is core to the scientific method, and code coverage is a worthwhile metrics, and it's not yet possible to run a Terminal or CLI tools in JupyterLite
- https://github.com/Carglglz/jupyter_upydevice_kernel would be cool to include in such a build in order to support MicroPython on Pi Pico W+, smart LEGO Boost & SPIKE Hubs with BLE, ESP32,
%pip install micropython pybricks pybricksdev pybricks-stubs pybricks-jedi circuitpython- https://github.com/Carglglz/jupyter_upydevice_kernel/issues/10
- https://news.ycombinator.com/item?id=35120757 :
- microsoft/vscode-python-devicesimulator lacks maintainers and Pi Pico Support: https://github.com/microsoft/vscode-python-devicesimulator/wiki/Deprecation-of-the-extension
- https://github.com/pybricks/support/issues/995
- https://github.com/microsoft/vscode/issues/135856
- How to write vscode.dev extensions: https://code.visualstudio.com/api/extension-guides/web-extensions
- you can connect vscode.dev to a remote VSCode instance over SSH and now https: https://code.visualstudio.com/docs/remote/vscode-server#_can-i-host-vs-code-the-vs-code-server-myself
- https://github.com/gitpod-io/openvscode-server
- ml-hub includes code-server in the ml-workspace docker image: https://github.com/ml-tooling/ml-workspace#visual-studio-code
- https://github.com/microsoft/vscode/wiki/How-to-Contribute#vs-code-for-the-web
VS Code for the Web Extensions and UI run in the browser.
👉 Besides
yarn watchalso runyarn watch-webto build the web bits for the built-in extensions.macOS and Linux
./scripts/code-web.sh