localdeps: Usage
localdeps is meant to be used as an easy way to install all dependencies of a conda package in development into a conda environment.
For example, let's say I'm developing a package named mypackage, and I want to package it as a conda package so other developers can conda install mypackage. The prescribed path to do this in the open source world is to publish as a package on pypi and then to create a feedstock using conda forge to publish the conda package.
If I'm working on closed source packages, I may need to build a conda package without publishing as a pypi package first. Here's the problem: conda does not provide a way to install a package or its dependencies listed in meta.yaml in a development environment the same way that pip does, so it becomes difficult to automate development environment setup.
So here comes localdeps to the rescue:
localdeps --conda-dir conda.recipe --env my-dev-env
pip install -e . --no-deps --no-build-isolation
Now, I only need one copy of the dependencies of my conda package (meta.yaml), and I can develop the code and have changes instantly take effect in the active environment.
Installation
conda install localdeps -c conda-forge
Note: This is not available via pip install because it depends on conda and conda-build, which are not available via pip.
Metadata
Release files for localdeps 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| localdeps-0.0.2.tar.gz | 4.3 kB | Without provenance | Details |
Release files / localdeps-0.0.2.tar.gz
| Download URL | localdeps-0.0.2.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62891d0854e6360a4545fe9991e30b0166f4e6ce6a5e9440afbaf61678093dfa
|
|
BLAKE2b-256 checksum How to use checksums |
d28cb91e7bb7d02810faff8547bca810040ab7c10430170fb707ab27d12c0bc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.0
|
Security for localdeps 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.