Open jtpio opened 2 years ago
%pip install pytest-cov hypothesis ipytest
$ pytest notebook.ipynb
would just work if:
%pip install micropython pybricks pybricksdev pybricks-stubs pybricks-jedi circuitpython
- microsoft/vscode-python-devicesimulator lacks maintainers and Pi Pico Support: https://github.com/microsoft/vscode-python-devicesimulator/wiki/Deprecation-of-the-extension
VS Code for the Web Extensions and UI run in the browser.
👉 Besides
yarn watch
also runyarn watch-web
to build the web bits for the built-in extensions.macOS and Linux
./scripts/code-web.sh
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:
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)