search

jupyterlite / xeus-python-kernel

xeus-python in JupyterLite
https://xeus-python-kernel.readthedocs.io
BSD 3-Clause "New" or "Revised" License
30 stars 19 forks source link

Update to JupyterLab 4 and JupyterLite 0.2.0 #155

Closed jtpio closed 10 months ago

jtpio commented 10 months ago

Technically the xeus python kernel works without modifications with JupyterLite 0.2.0a0: https://github.com/jupyterlite/jupyterlite/releases/tag/v0.2.0a0

But to keep dependencies correctly defined and avoid potential breakages we should consider updating to the latest packages.

github-actions[bot] commented 10 months ago

lite-badge :point_left: Try it on ReadTheDocs

jtpio commented 10 months ago

Before merging we might want to decide first how to handle versioning (and setup branches) so we can still make releases of the kernel for JupyterLite 0.1.x until 0.2.0 final is out.

martinRenou commented 10 months ago

Before merging we might want to decide first how to handle versioning (and setup branches) so we can still make releases of the kernel for JupyterLite 0.1.x until 0.2.0 final is out.

How about we plan a jupyterlite-xeus-python 1.x release with JupyterLite 0.2.0 support? So we get the full semver range afterwards.

Also, what would be the ETA for JupyterLite 0.2.0? Should we keep this PR open for now, waiting for this final release?

jtpio commented 10 months ago

How about we plan a jupyterlite-xeus-python 1.x release with JupyterLite 0.2.0 support? So we get the full semver range afterwards.

That would indeed be useful.

Also, what would be the ETA for JupyterLite 0.2.0? Should we keep this PR open for now, waiting for this final release?

There are some remaining issues listed in https://github.com/jupyterlite/jupyterlite/issues/1141. Then some other items like decoupling storage, but these could also go in a 0.3.0, so 0.2.0 is mostly focused on the lab 4 / nb 7 update.

Also we'll probably need a release of jupyterlite-xeus-python that supports JupyterLite 0.2.0 to be able to test it, now that https://github.com/jupyterlite/xeus-python-kernel/pull/160 is in.

martinRenou commented 10 months ago

Sure! So let's merge this one and make an 0.x branch + start making 1.x alpha releases.

jtpio commented 10 months ago

Also Meeseeks is enabled on the jupyterlite org, which should make it easier to do backports on branches.

martinRenou commented 7 months ago

meeseeksdev backport to 0.9.x

lumberbot-app[bot] commented 7 months ago

Something went wrong ... Please have a look at my logs.

It seems that the branch you are trying to backport to does not exist.

martinRenou commented 7 months ago

meeseeksdev backport to 0.x

lumberbot-app[bot] commented 7 months ago

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout 0.x
git pull

  1. Cherry pick the first parent branch of the this PR on top of the older branch:

    git cherry-pick -x -m1 8ed06f083b2e325af748e256e8a5e7118ec29a7e

  2. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #155: Update to JupyterLab 4 and JupyterLite 0.2.0'
  1. Push to a named branch:
git push YOURFORK 0.x:auto-backport-of-pr-155-on-0.x
  1. Create a PR against branch 0.x, I would have named this PR:

"Backport PR #155 on branch 0.x (Update to JupyterLab 4 and JupyterLite 0.2.0)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.