conda subprocess
Run a subprocess in a different conda environment.
Example
Create a new conda environment - in this example a conda environment for Python 3.12:
conda create -n py312 python=3.12
Subprocess Interface
Open a python shell in your base environment where conda_subprocess is installed and execute python --version in the
py312 environment:
from conda_subprocess import check_output
check_output("python --version", prefix_name="py312")
>>> b'Python 3.12.1\n'
Alternatively, the environment can be specified with the absolute path:
from conda_subprocess import check_output
check_output("python --version", prefix_path="/Users/janssen/mambaforge/envs/py312")
>>> b'Python 3.12.1\n'
As expected the process for the arguments for the subprocess call can also be defined as list:
from conda_subprocess import check_output
check_output(["python", "--version"], prefix_path="/Users/janssen/mambaforge/envs/py312")
>>> b'Python 3.12.1\n'
In addition to the check_output() function also the check_call() function is implemented:
from conda_subprocess import check_call
check_call("python --version", prefix_name="py312")
>>> Python 3.12.1
>>> 0
As well as the call() function:
from conda_subprocess import call
call("python --version", prefix_name="py312")
>>> Python 3.12.1
>>> 0
And the run() function:
from conda_subprocess import run
run("python --version", prefix_name="py312")
>>> Python 3.12.1
>>> CompletedProcess(args=['/bin/bash', '/var/folders/9p/rztyv06d0xv4h26cyv8nrw3m0000gq/T/tmpm8b8i0r3'], returncode=0)
As the CompletedProcess arguments illustrate conda_subprocess is internally writing the commands to a temporary file
for execution, to guarantee the conda environment is correctly activated.
For interactive communication conda_subprocess implements the Popen interface:
from subprocess import PIPE
from conda_subprocess import Popen
process = Popen(["python", "--version"], stdout=PIPE, prefix_name="py312")
process.communicate()
>>> (b'Python 3.12.1\n', None)
Decorator
In analogy to the subprocess interface the conda_subprocess also introduces the @conda decorator to
execute python functions in a separate conda environment:
from conda_subprocess.decorator import conda
@conda(prefix_name="py312")
def add_function(parameter_1, parameter_2):
return parameter_1 + parameter_2
add_function(parameter_1=1, parameter_2=2)
>>> 3
Remarks
- The
shellparameter and theenvparameter are not supported inPopen()and all derived methods. - The
pipesizeparameter and theprocess_groupparameter were removed for compatibility with python 3.9.
Metadata
Release files for conda-subprocess 0.0.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| conda_subprocess-0.0.12.tar.gz | 9.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| conda_subprocess-0.0.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.2 kB
Release files / conda_subprocess-0.0.12.tar.gz
| Download URL | conda_subprocess-0.0.12.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d03a33c97259ca032fbb051ea1901deddec768f9c81e309bfb9bc64754de7c9
|
|
BLAKE2b-256 checksum How to use checksums |
f7ad18a9029d06af0e7a6177c6968122b20ee4a3efc38cf29178e0a5b1581a8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logRelease files / conda_subprocess-0.0.12-py3-none-any.whl
| Download URL | conda_subprocess-0.0.12-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1fe9f375dba2684d212a0d81315b3d2bc284d6bd61e10312706616df15a1c0f9
|
|
BLAKE2b-256 checksum How to use checksums |
484150a92a4a3e03f4c3e47d38ff2392ac9ab1db7c004e190d528ed60cf631c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency log