This release is a pre-release and may not be stable for production use.
Ray is a unified framework for scaling AI and Python applications. Ray consists of a core distributed runtime and a set of AI libraries for simplifying ML compute:
Learn more about Ray AI Libraries:
Data: Scalable Datasets for ML
Train: Distributed Training
Tune: Scalable Hyperparameter Tuning
RLlib: Scalable Reinforcement Learning
Serve: Scalable and Programmable Serving
Or more about Ray Core and its key abstractions:
Tasks: Stateless functions executed in the cluster.
Actors: Stateful worker processes created in the cluster.
Objects: Immutable values accessible across the cluster.
Learn more about Monitoring and Debugging:
Monitor Ray apps and clusters with the Ray Dashboard.
Debug Ray apps with the Ray Distributed Debugger.
Ray runs on any machine, cluster, cloud provider, and Kubernetes, and features a growing ecosystem of community integrations.
Install Ray with: pip install ray. For nightly wheels, see the Installation page.
Why Ray?
Today’s ML workloads are increasingly compute-intensive. As convenient as they are, single-node development environments such as your laptop cannot scale to meet these demands.
Ray is a unified way to scale Python and AI applications from a laptop to a cluster.
With Ray, you can seamlessly scale the same code from a laptop to a cluster. Ray is designed to be general-purpose, meaning that it can performantly run any kind of workload. If your application is written in Python, you can scale it with Ray, no other infrastructure required.
More Information
Older documents:
Getting Involved
Platform |
Purpose |
Estimated Response Time |
Support Level |
|---|---|---|---|
For discussions about development and questions about usage. |
< 1 day |
Community |
|
For reporting bugs and filing feature requests. |
< 2 days |
Ray OSS Team |
|
For collaborating with other Ray users. |
< 2 days |
Community |
|
For asking questions about how to use Ray. |
3-5 days |
Community |
|
For learning about Ray projects and best practices. |
Monthly |
Ray DevRel |
|
For staying up-to-date on new features. |
Daily |
Ray DevRel |
5 maintainers
Metadata
5 maintainers
Release files for ant-ray-nightly 3.0.0.dev20241227
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ant_ray_nightly-3.0.0.dev20241227-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.17+ x86-64 | Details |
| ant_ray_nightly-3.0.0.dev20241227-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.17+ x86-64 | Details |
| ant_ray_nightly-3.0.0.dev20241227-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | CPython 3.9 | Linux glibc 2.17+ x86-64 | Details |
Total release size: 104.9 MB
Release files / ant_ray_nightly-3.0.0.dev20241227-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | ant_ray_nightly-3.0.0.dev20241227-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 35.0 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
9538b7826cf77ffc5463a1bccee616f591ca6cee91a16cac6a3a6be58c2632e1
|
|
BLAKE2b-256 checksum How to use checksums |
cd13a2b8405c5a9ced45a552cd783360139cac3888f6756379ae2204c89bf33b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Dec 27, 2024.
Transparency logRelease files / ant_ray_nightly-3.0.0.dev20241227-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | ant_ray_nightly-3.0.0.dev20241227-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 35.0 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
00cdbc12aaee590baf769a9098971017110f4829ca98c40d85b17ceb9c22e6d5
|
|
BLAKE2b-256 checksum How to use checksums |
c9d2ff0f2242d71f670e4f5876c3636d7791b2f82c2694a62411580caddbc6a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Dec 27, 2024.
Transparency logRelease files / ant_ray_nightly-3.0.0.dev20241227-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | ant_ray_nightly-3.0.0.dev20241227-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 34.9 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
03c257703e5c2324c1cc82edb2da2de2549f1ed3ba4218124ef222d603cbbc1c
|
|
BLAKE2b-256 checksum How to use checksums |
5b3ae908931f4f375cf8f14c67c3306b472dd5adfc39df823e5072c026c05959
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Dec 27, 2024.
Transparency log
