Python Bindings for UCX
Installing
Users can either install with Conda or build from source.
Testing
To run ucx-py's tests, just use pytest:
pytest -v
TCP Support
In order to use TCP add tcp to UCX_TLS and set UCXPY_IFNAME to the network interface you want to use. Some setup examples:
# TCP using "eth0" and CUDA support
export UCX_TLS=tcp,cuda_copy,cuda_ipc
export UCXPY_IFNAME="eth0"
# InfiniBand using "ib0" and CUDA support
export UCX_TLS=rc,cuda_copy,cuda_ipc
export UCXPY_IFNAME="ib0"
# TCP using "eno0" and no CUDA support
export UCX_TLS=tcp
export UCXPY_IFNAME="eno0"
Metadata
Release files for ucx-py-cu11 0.44.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ucx_py_cu11-0.44.0.tar.gz | 1.4 kB | Without provenance | Details for ucx_py_cu11-0.44.0.tar.gz |
Release files / ucx_py_cu11-0.44.0.tar.gz
| Download URL | ucx_py_cu11-0.44.0.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b1f15c648782fa0409cbbc2a7128430956f6102dba7ffa96c7c4b385b32ffb2
|
|
BLAKE2b-256 checksum How to use checksums |
4c350d0db159e047f2880f8e1206025650a7763ffbc29c51ed165fedfa9e84a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.18
|
Security for ucx-py-cu11 0.44.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
