Registry / devops / py-rattler

py-rattler

JSON →
library0.25.0pypypi✓ verified 86d ago

A blazing fast Python library to work with the conda ecosystem, built on top of the Rust rattler libraries. Current version 0.23.2. Release cadence is active, with frequent updates.

pip install py-rattler
INSTALL
IMPORT
SIG · PY-RATTLER
P
py-rattler
devopspythonv0.25.0
Install
2.1s avg
Import
156ms
Disk
73MB
Pass rate
10/ 10
Env Coverage10 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v0.25.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.95 runs
installs and imports cleanly · install 0.0s · import 0.158s · 73.4MB
glibc
py 3.103.95 runs
installs and imports cleanly · install 2.1s · import 0.154s · 77MB
73MB installed
● package 73MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

Gateway
from rattler import Gateway
from rattler import CondaGateway
CondaGateway was renamed to Gateway in v0.20
solve
from rattler import solver
from rattler import solve
The module is named solver, not solve

Basic example: query conda-forge for package information.

import os from rattler import Gateway, Channel, PrefixRecord # Initialize gateway with custom channels gateway = Gateway() # Query some packages package_names = ["python", "numpy"] channel = Channel("conda-forge") for name in package_names: pkg_info = gateway.query(channel, name) print(f"Latest version of {name}: {pkg_info[0].version if pkg_info else 'not found'}")
Debug
Known issues
breakingIn v0.20, the main module was renamed from rattler_conda to rattler. Import paths changed.
fix
Use `from rattler import ...` instead of `from rattler_conda import ...`
affects: <0.20
gotchaThe solver module is named 'solver', not 'solve'. Many first-timers import the wrong name.
fix
Use `from rattler import solver`
affects: all
gotchaGateway constructor may need a custom prefix or channels. By default it uses the current conda environment.
fix
Explicitly pass channels or prefix when creating Gateway if needed.
affects: all
Errors
Common errors & fixes
ModuleNotFoundError: No module named 'rattler_conda'
Outdated import path from version <0.20
fix
Change import to `from rattler import ...`
AttributeError: module 'rattler' has no attribute 'solve'
Attempted to import 'solve' instead of 'solver'
fix
Use `from rattler import solver`
rattler.gateway.GatewayError: failed to load repodata
Network issues or incorrect channel URL
fix
Verify channel URL is valid and you have internet access. Use explicit channel like `Channel('conda-forge')`
Upgrade
Version history
0.25.0latest on PyPI · released Jun 9, 2026
Audit
Dependencies
certifirequiredRequired for HTTPS requests
Agent activity
12 hits · last 30 days
node
6
Resources