Readit Newsokost1 commented on Show HN: Juvio – UV Kernel for Jupyter github.com/OKUA1/juvio... · Posted by u/okost1
Would it work on Jupyter lite?
Unfortunately it won't, at least due to the fact UV is not available in the in-browser/wasm ecosystem. That would be awesome though. Maybe it is possible to make something close in terms of functionality using a custom pyodide kernel + micropip, but I did not look into that.
okost1 commented on Show HN: Juvio – UV Kernel for Jupyter github.com/OKUA1/juvio... · Posted by u/okost1
Seems awesome ! I'll try it soon.
Thank you! I am looking forward to your feedback.
okost1 commented on Show HN: Juvio – UV Kernel for Jupyter github.com/OKUA1/juvio... · Posted by u/okost1
See also: juv
Hi. Thanks for bringing this up. To be honest, I have never tried juv, but judging from the readme the ideas of juv and juvio are slightly different. In juvio the ephemeral environment is created on kernel startup. Hence, one can have multiple notebooks within the same jupyterlab session, each with its own venv. This seems to be different with juv, but please correct me if I am wrong.
okost1 commented on Show HN: Juvio – UV Kernel for Jupyter github.com/OKUA1/juvio... · Posted by u/okost1
> Why Use Juvio?
> No additional lock or requirements files are needed
Additional to what?
> Guaranteed reproducibility
Of what?
I probably need your project, but I don't understand what it is for.
Hi. I appreciate your feedback. Basically, juvio stores all of the project requirements (versions of the packages and of the python interpreter) directly within the notebook itself using the PEP 723 spec. Then, when you open the notebook, a new ephemeral environment is created on the fly with all of the required dependencies. Therefore, you don't have to maintain a separate e.g. requirements.txt/conda.yaml/uv.lock file.
2. LUML is an end-to-end platform, so it has a much larger scope than MLFlow.