envd
envd copied to clipboard
feat: Support conda/pip requirement file
SGTM. I think we should recommend users write deps in build.envd, but we should not be extreme. We should support requirements.txt.
Users also expect that we can support this.
- [x] Support requirements.txt
- [ ] Support conda env.yaml
/assign
The syntax of requirement.txt is complex (link). However current implementation can cover most common usages I believe.
One question:
--find-links https://download.pytorch.org/whl/torch_stable.html torch==1.9.0+cu102 ...For example in dgl usage, will
--find-links https://download.pytorch.org/whl/torch_stable.htmlbe considered as a package when listing the dependency?
Yep, I think so. We just ignore comment. And every line starts without # will be considered to be a dependency.
Maybe we should mount the file into the build process, and use the file directly to install dependencies.
Originally posted by @gaocegege in https://github.com/tensorchord/envd/issues/484#issuecomment-1162705326
[x] Support requirements.txt
- [ ] Support conda env.yaml
- conda env.yaml is supported in #674, should we close this issue?