rapids-dask-dependency
Dask and Distributed version pinning for RAPIDS
Decision gist · record as of 2026-08-14
Yes, if you are using RAPIDS packages. This metapackage is essential for RAPIDS users to ensure Dask compatibility and automatic patching. It has no direct use outside RAPIDS environments and should not be installed standalone. For RAPIDS users, it is a required dependency managed by RAPIDS packages themselves, not typically installed directly.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Intended for use within RAPIDS environments; manual import is not supported and patches are applied automatically via site initialization.
- Active maintenance with a release 8 days ago.
- Low install friction—a pure Python wheel with only dask and distributed as runtime dependencies.
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows use in most commercial and open-source projects without significant restrictions.
last release 2026-08-06 (8 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 251,620 downloads/mo, #8,572 on PyPI
Alternatives
Verify before relying
pip install rapids-dask-dependency==26.8.0
# No manual import needed; the package installs a .pth file that automatically
# patches dask modules on Python interpreter startup when RAPIDS packages are present.- Specific dask and distributed versions pinned by this release (26.8.0) are not listed in the fact sheet.
- Scope and nature of RAPIDS-specific patches applied to dask modules.
- Whether the package works correctly with Python versions not explicitly declared in requires_python.
What it is and what it does
rapids-dask-dependency is a metapackage that centralizes Dask version pinning across RAPIDS releases. Because Dask's API changes between releases, each RAPIDS version must lock to a specific Dask and distributed pair to avoid incompatibilities. This package encodes those pinned versions and makes them available as a single dependency.
Beyond version pinning, the package includes a patching mechanism that runs on Python startup. It installs a .pth file and a custom meta path loader that intercepts all dask module imports and applies RAPIDS-specific patches automatically. This ensures dask modules are always compatible with RAPIDS regardless of import order, and users never need to manually import or configure it—it activates transparently when RAPIDS packages are installed.
Use it for
- Installing RAPIDS packages that depend on a specific Dask version without manually managing version conflicts.
- Ensuring dask modules are patched for RAPIDS compatibility automatically on interpreter startup.
- Building RAPIDS nightly environments where alpha-tagged versions of the metapackage must be pinned with CalVer constraints.
- Centralizing Dask dependency management across multiple RAPIDS packages in a single release.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are using RAPIDS packages.
This metapackage is essential for RAPIDS users to ensure Dask compatibility and automatic patching. It has no direct use outside RAPIDS environments and should not be installed standalone. For RAPIDS users, it is a required dependency managed by RAPIDS packages themselves, not typically installed directly.
Install
rapids-dask-dependency on PyPI
Before you install
Active maintenance with a release 8 days ago. Low install friction—a pure Python wheel with only dask and distributed as runtime dependencies.
Intended for use within RAPIDS environments; manual import is not supported and patches are applied automatically via site initialization.
License in practice
Apache-2.0 permissive license allows use in most commercial and open-source projects without significant restrictions.
Quickstart
pip install rapids-dask-dependency==26.8.0
# No manual import needed; the package installs a .pth file that automatically
# patches dask modules on Python interpreter startup when RAPIDS packages are present.Verify before relying
- Specific dask and distributed versions pinned by this release (26.8.0) are not listed in the fact sheet.
- Scope and nature of RAPIDS-specific patches applied to dask modules.
- Whether the package works correctly with Python versions not explicitly declared in requires_python.
Package facts
| License | Apache-2.0 permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesdaskdistributed |
| Maintenance | Actively maintained 8 days since the last release |
| First released | |
| Downloads | 251,620 / month, #8,572 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: rapids_dask_dependency-26.8.0-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 › “dask version pinning”
- rapids-dask-dependencyPins compatible versions of dask and distributed for RAPIDS packages,…
- oldest-supported-numpyProvides the oldest version of NumPy compatible with a given Python…
- webdriver-managerAutomatically downloads, caches, and manages browser driver binaries…
Give your agent the search over MCP, or paste the wish link into any chat.
More Distributed Computing packages
gRPC Python is an HTTP/2-based RPC framework that enables you to define and call remote procedures across network boundaries using protocol buffers for serialization.
Install it if you need RPC communication in a distributed system or are integrating with existing gRPC services.
execnet lets you spawn and communicate with Python interpreters across local processes, remote hosts, and different platforms, using a simple API for task distribution and inter-process messaging.
However, the aging maintenance status (275 days since last release) means you should verify it meets your concurrency and performance needs before committing to a…
Cloudpickle extends Python's standard pickle module to serialize lambda functions, interactively-defined functions and classes, and other constructs that the default pickle cannot handle, making it suitable for cluster computing and remote code execution.
Install it if you need to serialize lambda functions, interactively-defined code, or non-standard Python constructs for cluster computing or distributed execution.
Provides a unified, open()-compatible Python API for streaming large files from remote storage (S3, GCS, Azure, HDFS, SFTP, HTTP) and local filesystems, with transparent compression support.
Install it if you work with large files on cloud storage or remote systems and want to avoid writing boilerplate around multiple SDKs.
Portalocker provides cross-platform file locking with support for exclusive and shared locks, plus Redis-based distributed locks and process-aware PID file locking.
Install it if you need file or process coordination; the optional extras (pywin32, redis) are only required for specific lock types.
Ray is a distributed computing framework that scales Python applications from a single machine to multi-node clusters, providing abstractions for parallel tasks, stateful actors, and shared objects.
See also dask-cuda · raft-dask-cu12 · pins · distributed-ucxx-cu12 · rapids-logger · donfig · dask-awkward · sail-sdk · dask-cudf-cu12 · prefect-dask