Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relocate requirements.txt #26

Open
JAlvarezJarreta opened this issue Aug 22, 2024 · 3 comments
Open

Relocate requirements.txt #26

JAlvarezJarreta opened this issue Aug 22, 2024 · 3 comments

Comments

@JAlvarezJarreta
Copy link

Hello, I was wondering if it would be possible to relocate the requirements.txt file currently located inside the ui folder to the root of the repository? Most tools and Python systems expect these type of files (e.g. requirements.txt, pyproject.toml) to be located at the root, and not having these file in that setup in this case is affecting our automatic environment creation system. Thank you very much in advance!

@victzh
Copy link

victzh commented Aug 22, 2024

Out of curiosity, what automatic environment creation system do you use? We'll move the file in the next release certainly, it was there originally just to keep it along with the Python script - the rest of the code is NextFlow.

@JAlvarezJarreta
Copy link
Author

Thank you very much!

To answer your question, we have an in-house system in Ensembl created around venv to put all the virtual environments in an advisable location inside our cluster, so these can be accessed/loaded/listed in a similar fashion to what pyenv does, but with a significantly smaller footprint (we centralise the common Python versions and libraries, so these are only installed once for all the users). The implementation of this system was based on the premise that all repositories with Python code will have their pyproject.toml, setup.py and requirements*.txt files in the root, as it is the standard. Thus the request.

@victzh
Copy link

victzh commented Aug 23, 2024

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants