Open yuvipanda opened 1 year ago
As an upstream, I'd caution that doing anything 1.0-related to jupyterlite is kind of premature... we have wantonly broken API on a number of occasions, no semver, etc. My experience is folks have pretty high expectations of Actions working securely, forever, on all platforms without having to do any work or maintenance, and lite isn't ready to support that yet.
If this repo does want to push forward, it should hard pin to a specific 0.1.0bXX
tested against a wide swathe of types of repos, and do a major version bump when a stable 0.1.0
jupyterlite lands.
figure out how to disable specific kernels
To that end, the first non --pre
release where it would start caring and documenting API stability likely will have a package that doesn't include any pyodide-based kernel, or any kernels, for that matter.
As mentioned elsewhere, I am not a fan of [extras]
, as pip
basically drops them on the floor outside of the context of a single -r requirements.txt
solve. So it's likely we'll end up with a number of packages:
cut from the monorepo:
jupyterlite-core
doit
and jupyter_core
jupyterlite-repl-app
jupyterlite-lab-app
jupyterlab
(to get matching extension versions, contents, translations)jupyterlite-notebook-app
retrolab
(to get matching extension versions, contents, translations)jupyterlite
pyodide
and js
kernelscut from other repos, depending on jupyterlite-core
jupyterlite-js-kernel
jupyterlite-pyodide-kernel
pkginfo
for .whl
parsing I know lots of folks are scared around calling things 1.0. Maybe I can just call it '1'? I just like large numbers, and for applications and tools, (rather than libraries), faster releases seem better.
Should be fairly soon! Things to do before that:
.
folders