Tags: conda-incubator/conda-project
Tags
[chore] support conda-lock 2 and 3 (#184) * support conda-lock 2 and 3 * conda-lock 2 and 3 in CI * wrong args for conda-lock 2 * missed two pins * ignore coverage in _conda_lock wrapper * test 3.13 * conda-forge in tests * Update main.yaml * Update test_install.py How did that ever work? * missed one * one-step env creation in actions * List dependencies
support pydantic 2 (#146) * support pydantic 2 using the v1 fallback for now * missed one * switch libmamba install order * get version into CI/CD build * version assert in conda.recipe * switch to hatch * conda-forge * so close * Update meta.yaml * Update main.yaml * Almost there * One more 🤞 * packaging updates * try to fix conda-build step exit 1 * add pypi publish * 😔 so close * maybe without setupminiconda
[pre-commit.ci] pre-commit autoupdate (#139) * [pre-commit.ci] pre-commit autoupdate updates: - [github.com/pre-commit/pre-commit-hooks: v4.4.0 → v4.5.0](pre-commit/pre-commit-hooks@v4.4.0...v4.5.0) - [github.com/pycqa/isort: 5.12.0 → 5.13.2](PyCQA/isort@5.12.0...5.13.2) - [github.com/psf/black: 23.7.0 → 24.1.1](psf/black@23.7.0...24.1.1) - [github.com/pycqa/flake8: 6.1.0 → 7.0.0](PyCQA/flake8@6.1.0...7.0.0) - [github.com/Lucas-C/pre-commit-hooks: v1.5.1 → v1.5.4](Lucas-C/pre-commit-hooks@v1.5.1...v1.5.4) * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Experimental features: run with external-environment and project arch… …ive download/extract (#106) External environment and archive download/extract ## External environment You can run commands using conda environments not managed by the project itself. `conda project run --external-environment=<env> [command] [args ...]` Where `<env>` can be a relative or absolute path to a conda environment, or the name of a global environment stored in one of `envs_dirs` directories. If there is a collision between a local environment directory and named environment, the local environment directory is preferred. If no local environment directory found it will check through the conda config "envs_dirs" in order and return the first matching named environment. ~In this PR a defined environment is not required.~ ## Download and extract a project archive Two new flags are added `--project-archive` and `--archive-storage-options` ``` --project-archive PROJECT_ARCHIVE_FILE_OR_URL EXPERIMENTAL: Extract and run directly from a project archive. The archive can be a local file or a fsspec compatible URL. You may need to install appropriate driver packages to work with remote archives. Optionally, use --directory to set the destination directory of the extracted project. --archive-storage-options ARCHIVE_STORAGE_OPTIONS EXPERIMENTAL: Comma separated list of fsspec storage_options for accessing a remote archive For example --archive-storage-options username=<user>,password=<pass> ``` These flags are enabled for * lock * check * install * activate * run
PreviousNext