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
Currently, our implementation of PyPI dependencies completely ignores lock files. We have to add back support to check the satisfyability of our constraints against a lock file where PyPI dependencies are also involved.
The biggest hurdle in this process is that in the lock-file we currently have no mapping from conda package names to PyPI package names. This will most likely have to be added to the lock-file format to ensure we can deterministically verify the satisfyability of the lock-file without requiring any internet connection.
The text was updated successfully, but these errors were encountered:
This PR adds support for checking the satisfiability of the lock-file
which includes pypi-dependencies.
Purls have been added to the lock-file
(conda/rattler#414) (See also:
conda/ceps#63). This enables checking
which conda packages will install which pypi packages without needing to
check the internet. This ensures we can still check if a lock-file is up
to date quickly.
I did not profile this code but I think there are a lot of places we can
improve the performance. Thats for a later PR.
I also didn't add tests. I think we should but we can also do that in
another PR.
Closes#467
---------
Co-authored-by: Ruben Arts <[email protected]>
Currently, our implementation of PyPI dependencies completely ignores lock files. We have to add back support to check the satisfyability of our constraints against a lock file where PyPI dependencies are also involved.
The biggest hurdle in this process is that in the lock-file we currently have no mapping from conda package names to PyPI package names. This will most likely have to be added to the lock-file format to ensure we can deterministically verify the satisfyability of the lock-file without requiring any internet connection.
The text was updated successfully, but these errors were encountered: