-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.3.0 Release Plan #1228
Comments
Is there a rough idea for 0.3.0 ETA, now that jupyterlab-4.1rc1 is out ? |
Just created the |
Yes, we had listed a couple of items above that would have been nice to have in So since #1263 now seems to be ready to go, we could also make a |
|
This is an issue for the
0.3.0
release planning.Features
Contents via custom drives
Users have been asking for ways to integrate JupyterLite with extra sources of content, potentially hosted remotely:
As part of the
0.3.0
release, we should consider making the necessary changes to allow for better integration with custom drives. This could likely require breaking changes, since kernels expect to know information about drives at the moment:Pyodide
https://github.com/jupyterlite/pyodide-kernel/blob/143526c9e11589b03c8d6844be5471d527b76255/packages/pyodide-kernel/src/worker.ts#L23-L30
https://github.com/jupyterlite/pyodide-kernel/blob/143526c9e11589b03c8d6844be5471d527b76255/packages/pyodide-kernel/src/worker.ts#L117-L124
Xeus Python
https://github.com/jupyter-xeus/xeus-lite/blob/07df211bc73c1002558017b86499d63806d133d6/share/xeus-lite/web_worker_kernel.ts#L164-L171
https://github.com/jupyter-xeus/xeus-lite/blob/07df211bc73c1002558017b86499d63806d133d6/share/xeus-lite/worker.ts#L119-L126
Related issues:
Contents.IDrive
for the JupyterLite in-browser contents manager #1041IDrive
jupyter/notebook#6665RTC
Related to the section above about custom drives, we should look into bringing back support for RTC.
Ideally an improved support of drives would be enough to develop the RTC extension separately from this repo, in its own drive.
The text was updated successfully, but these errors were encountered: