jupyterlite/xeus-wren-kernel

polish / cleanup this repo

Opened this issue · 12 comments

DerThorsten commented

@jtpio I cleaned up the Dockerfile, but I assume it does not make sense to add further changes here before we have the "common" code (https://github.com/jupyterlite/xeus-kernel/tree/experiments) ready

jtpio commented

Right. We should make the CI pass on this repo first anyway.

DerThorsten commented

@jtpio ci is passing, should we put it on PyPi?

jtpio commented

Sure. I can create an empty jupyterlite-xeus-wren package on PyPI as a placeholder so we can generate tokens for it.

Then we could use the releaser to publish it there.

jtpio commented

@DerThorsten I can do the initial release, but will need write access to the repo for that

DerThorsten commented

you should have an invitation @jtpio

jtpio commented

Thanks!

DerThorsten commented

@jtpio there is also https://github.com/DerThorsten/jupyter_wren_syntax to have some syntax highlighting for wren. There is a conda-forge PR, but unfortunately it builds only for mac and win....oddly it does not run on linux and fails with a conda unsatisfiable dependency error
but for jupyerlite we can live without a conda package. I assume we would need to put this on npm to use this in the juyterlite kernel

jtpio commented

Or we also publish that package to PyPI.

Looks like this is a JupyterLab prebuilt / federated extension so it should also work out of the box in JupyterLite.

jtpio commented

Or we also publish that package to PyPI.

In that case we can do something similar:

jtpio commented

jupyterlite-xeus-wren is live on this custom JupyterLite deployment: https://jtpio.github.io/lit

image

  • 🎉1
DerThorsten commented

awesome!
Should we use this for the blogpost or rather have one jupyterlite with everything?

jtpio commented

I think they could be added to https://github.com/jupyterlite/demo.

Will look into releasing jupyterlite-xeus-lua next. We can do the refactor with the common xeus code later.

  • 👍1