-
Notifications
You must be signed in to change notification settings - Fork 10
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
Switch to a federated serverlite extension #1
Conversation
Just thinking out loud: the happy path might be:
easy, right!? |
return json.load(f)["version"] | ||
version = json.load(f)["version"] | ||
return ( | ||
version.replace("-alpha.", "a") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blearg, how many times have i written this 🤣
Should we also |
Yes sounds good 👍 At least if we continue shipping it by default. Otherwise it would be using its own copy of |
Yes, which should almost correspond to the current state of jupyterlite/jupyterlite#352. I'll finish this PR and cut a first release of For the name of the federated kernel, we could go for:
The second sounds good, but would be fine with the first one too. Later we can imagine having |
|
Should be good to go for a first iteration. We can iterate in follow-up PRs. |
Continue the switch to a federated serverlite extension:
TODO
0.1.0-alpha.x
versioningliteExtension
key to thepackage.json
to indicate this is not a regular lab extensionjupyterlite-p5-kernel
?PyPI
: https://pypi.org/project/jupyterlite-p5-kernel/