Currently jupyterlite-xeus-python supports reading dependencies from an environment.yml file which is great :+1:
However some folks new to Python and likely to use JupyterLite might not be familiar with the whole conda world of packages. This might not be an issue if they are just using an existing JupyterLite site. However it could become one if they want to build their own site.
Proposed Solution
Maybe the kernel addon could also support reading dependencies from a requirements.txt if available. And "translate" it to an environment.yml transparently before triggering the build.
Problem
Currently
jupyterlite-xeus-python
supports reading dependencies from anenvironment.yml
file which is great :+1:However some folks new to Python and likely to use JupyterLite might not be familiar with the whole conda world of packages. This might not be an issue if they are just using an existing JupyterLite site. However it could become one if they want to build their own site.
Proposed Solution
Maybe the kernel addon could also support reading dependencies from a
requirements.txt
if available. And "translate" it to anenvironment.yml
transparently before triggering the build.This might need https://github.com/jupyterlite/xeus-python-kernel/pull/102 first, as not all packages on PyPI are available on conda-forge.
Additional context
This came up in discussions after the presentation about JupyterLite at a Python meetup: https://www.meetup.com/fr-FR/groupe-dutilisateurs-python-grenoble/events/291818929/