Skip to content
This repository has been archived by the owner on Feb 14, 2024. It is now read-only.

Support requirements.txt #121

Open
jtpio opened this issue Mar 31, 2023 · 1 comment
Open

Support requirements.txt #121

jtpio opened this issue Mar 31, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@jtpio
Copy link
Member

jtpio commented Mar 31, 2023

Problem

Currently jupyterlite-xeus-python supports reading dependencies from an environment.yml file which is great 👍

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.

This might need #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/

@jtpio jtpio added the enhancement New feature or request label Mar 31, 2023
@jtpio
Copy link
Member Author

jtpio commented Mar 31, 2023

An alternative would be to just document:

  • how to translate a requirements.txt to an environment.yml file
  • explain the differences between the two
  • explain what conda, conda-forge and escripten-forge are

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant