You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The [tool.conda-lock.dependencies] section in pyproject.toml allows one to specify Conda-only dependencies that aren't available via pip. I propose a [tool.conda-lock.dev-dependencies] section for development dependencies only available via Conda.
For example, consider that you want to install git at the latest version as a development dependency but not have this be part of your production dependencies. This is a current requirement of my company since we use newer features in git for our development.
Furthermore, I'm writing a script to generate a meta.yaml (conda-build) using conda-lock. This would help me avoid pulling in git as a dependency of my Conda package when other users install it.
If the authors like this feature suggestion, let me know how trivial it might be to add it and where is the best place for me to look in the code. I'd be happy to try to open a PR. Also open to other ways to achieve this.
The text was updated successfully, but these errors were encountered:
wesleykendall
changed the title
Feature request: Support [tool.conda-lock.dev-dependencies] section in pyproject.toml
Feature equest] Support [tool.conda-lock.dev-dependencies] section in pyproject.toml
Mar 7, 2022
wesleykendall
changed the title
Feature equest] Support [tool.conda-lock.dev-dependencies] section in pyproject.toml
[Feature Request] Support [tool.conda-lock.dev-dependencies] section in pyproject.toml
Mar 7, 2022
@mariusvniekerk My understanding of optional dependencies after reading pep621 are that they are optional production dependencies. For example, the pip_support optional dependency for conda-lock.
git would only be for development/CI purposes and never pulled into a production install, which is effectively how poetry.dev-dependencies works.
Hope that makes sense. Are you able to point me to the exact place where conda-lock parses the tool.poetry.dev-dependencies section? It might make more sense if I can open a quick PR to illustrate
The
[tool.conda-lock.dependencies]
section in pyproject.toml allows one to specify Conda-only dependencies that aren't available via pip. I propose a[tool.conda-lock.dev-dependencies]
section for development dependencies only available via Conda.For example, consider that you want to install
git
at the latest version as a development dependency but not have this be part of your production dependencies. This is a current requirement of my company since we use newer features in git for our development.Furthermore, I'm writing a script to generate a
meta.yaml
(conda-build) using conda-lock. This would help me avoid pulling ingit
as a dependency of my Conda package when other users install it.If the authors like this feature suggestion, let me know how trivial it might be to add it and where is the best place for me to look in the code. I'd be happy to try to open a PR. Also open to other ways to achieve this.
The text was updated successfully, but these errors were encountered: