Closed pep-sanwer closed 8 months ago
Name | Link |
---|---|
Latest commit | 3d2c384405a07cb7cd00f09aa82f3d4b232f1ee4 |
Latest deploy log | https://app.netlify.com/sites/conda-lock/deploys/65299e626cee23000894b0a1 |
Deploy Preview | https://deploy-preview-527--conda-lock.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
@maresb, great catch! Completely forgot tests for the other flavors! Yes you are right, this does apply across all flavors of pyproject.toml
. Requested changes amended into commit! (Requested changes in above force push, typo fixes in below force push). Additionally added missing requires-python
in flit
test pyproject.toml
s.
Appreciate the incredibly speedy feedback!
This introduces a new flag for
pyproject.toml
-based specification (affecting all flavors ofpyproject.toml
) that skips locking / solving for all dependencies not found under[tool.conda-lock]
.This allows use-cases where a user wants
conda-lock
locking for only conda dependencies, while bringing their own locker for other dependencies. (My preferred workflow isconda-lock
for venv management / management of any non-pip-able deps, followed bypoetry
for pip-able deps).The flag is exposed as:
The below example
pyproject.toml
:would result in
conda-lock
only producing a lockfile forpython
,sqlite
, andcertifi
, skippingpandas
andnumpy
.Again, deeply appreciative of this incredible tool, and for your time in reviewing this PR. Very open to suggestions / refinements.