conda-inject
Helper functions for injecting a conda environment into the current python environment (by modifying sys.path, without actually changing the current python environment).
Decision gist · record as of 2026-08-14
Yes, if you need lightweight runtime injection of conda packages and can tolerate dormant maintenance. The low install friction and lack of vulnerabilities make it safe to try. However, verify the undeclared license for your use case, and be aware that no active maintenance means no bug fixes or updates. Consider it a stable utility rather than an actively developed tool.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.9 or later.
- The package modifies sys.path at runtime; ensure the target conda environment path is valid and accessible.
- Low install friction with a single runtime dependency (pyyaml).
License · maintenance · safety
(unclear) — License status is unclear; no SPDX identifier or raw license text is available. Verify the actual license before use in proprietary or copyleft-sensitive contexts.
last release 2024-05-27 (809 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 111,859 downloads/mo, #12,393 on PyPI
Alternatives
Verify before relying
pip install conda-inject
import conda_inject
conda_inject.inject_conda_env('/path/to/conda/env')- What specific functions does the package export and what are their signatures?
- Does the package handle conda environment discovery, or must the path be provided explicitly?
- Are there known edge cases or limitations when injecting multiple environments or conflicting package versions?
What it is and what it does
conda-inject is a utility for dynamically loading packages from a conda environment into your current Python process without activating that environment. It works by manipulating sys.path to prepend the target environment's site-packages directory, making its packages importable as if they were installed in the active environment. This is useful when you need to access packages from a specific conda environment without the overhead or side effects of full environment activation.
The package depends only on pyyaml and supports Python 3.9, 3.10, 3.11, and 3.12. It is currently dormant—last release was 2024-05-27—so it receives no active maintenance. The license is undeclared, which may be a concern for some use cases.
Use it for
- Load packages from an isolated conda environment in a script without activating it.
- Dynamically switch between multiple conda environments' packages within a single Python session.
- Test compatibility of code against packages from a specific conda environment without environment switching overhead.
- Integrate conda-managed dependencies into a containerized or CI/CD workflow where full activation is impractical.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need lightweight runtime injection of conda packages and can tolerate dormant maintenance.
The low install friction and lack of vulnerabilities make it safe to try. However, verify the undeclared license for your use case, and be aware that no active maintenance means no bug fixes or updates. Consider it a stable utility rather than an actively developed tool.
Install
conda-inject on PyPI
Before you install
Low install friction with a single runtime dependency (pyyaml). Package is dormant—no releases recorded in recent years—so expect no active maintenance or bug fixes.
Requires Python 3.9 or later. The package modifies sys.path at runtime; ensure the target conda environment path is valid and accessible.
License in practice
License status is unclear; no SPDX identifier or raw license text is available. Verify the actual license before use in proprietary or copyleft-sensitive contexts.
Quickstart
pip install conda-inject
import conda_inject
conda_inject.inject_conda_env('/path/to/conda/env')Verify before relying
- What specific functions does the package export and what are their signatures?
- Does the package handle conda environment discovery, or must the path be provided explicitly?
- Are there known edge cases or limitations when injecting multiple environments or conflicting package versions?
Package facts
| License | Not declared unclear |
| Python support | Supports the current Python release <4.0,>=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagepyyaml |
| Maintenance | Dormant 809 days since the last release |
| First released | |
| Downloads | 111,859 / month, #12,393 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Programming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.9 |
Evidence: conda_inject-1.3.2-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “conda environment path injection”
- conda-injectInjects a conda environment's packages into the current Python…
- ensurecondaA CLI tool that finds or installs a conda/mamba executable, returning…
- findlibsLocates shared libraries on the system by searching Python packages,…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also doppler-env · inject · locate · dependency-injector · coherent.licensed · injector · juliapkg · frida · in-n-out · rootpath