Open moi90 opened 11 months ago
I'm not saying no, but I'm not convinced that we should support this.
Anything wrong with replacing that line with conda-lock -f environment.base.yaml -f docs/requirements.txt
?
Anything wrong with replacing that line with
conda-lock -f environment.base.yaml -f docs/requirements.txt
?
docs/requirements.txt
is only a dev requirement, so that would not quite work as intended. Or is there a way to specify a category
in a requirements.txt
, maybe via a comment?
Oh, that's very interesting! I think we're missing this feature. A comment seems like a reasonable way to provide this info. I'm not sure the best way to design the specification. Do you have any suggestions?
CC: @mariusvniekerk
The documentation only talks about environment.yml
, meta.yml
and pyproject.toml
as source formats. I didn't even know that requirements.txt
is also a valid input format. So this is a great opportunity to improve the documentation :)
Regarding the exact format: Maybe something like #category: dev
, #!category: dev
or #--category dev
? Is there some de-facto standard to include metadata in comments?
Ah, my bad, we don't support requirements.txt
yet. I was confused since almost all the code to accomplish this exists already. This should be fairly straightforward to implement. (Look under conda_lock/src_parser
.) Would you be interested in submitting a PR?
Regarding the format, of your suggestions I personally prefer the first.
I'm currently not able to provide a PR, sorry. But it's great that so much is already in place.
Checklist
What happened?
The environment is defined as follows:
Including
requirements.txt
in this way is allowed by conda. However, withconda-lock -f environment.base.yml
, I get the following error:Conda Info
Conda Config
Conda list
No response
Additional Context
No response