MORPH
SIGN IN SIGN UP
ray-project / ray UNCLAIMED

Ray is an AI compute engine. Ray consists of a core distributed runtime and a set of AI Libraries for accelerating ML workloads.

41876 0 1 Python
Normal View History Raw
[ci] add python >= 3.10 for gymnasium to make windows CI happy (#59572) we can remove the python version constraint after windows CI is migrated to python 3.9 Signed-off-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com> Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
2025-12-19 05:45:00 -08:00
# These are mirrored in setup.py as install_requires,a
*: Centralize requirements.txt and unify dependency versions (#9759) * python_test: fix cython_examples in doc/ and tests/ * update setup.py to parse the bazel version string better * all: centralize all python deps into stackable requirements files in python/ * format * Move cython test into the proper package * Add cross-reference dependency comments for requirements and setup.py * re-enable version pinning on CI, fix formatting * fix up torchvision version * fix case in shell
2020-07-30 11:22:56 -07:00
# which is what the users of the ray package will install. The rest of this file
# sets up all the packages necessary for a /developer/ of Ray.
#
# In short, if you change it here, PLEASE also change it in setup.py.
[RLlib] Atari gym environments now require ale-py. (#28703)
2022-09-22 19:05:54 +02:00
[docker] Fix requirements files and installation in docker images (#29375) Requirements installation is currently broken by a glob: The `python/requirements/data_processing/requirements.txt` overwrites the `python/requirements.txt` in a glob copy operation. This leads the docker images to have faulty and incompatible dependencies installed. This PR refactors the requirements management in Ray. In short: * the `python/requirements.txt` will only contain constraints defined in `setup.py` * A new `python/requirements_test.txt` will contain _pinned_ dependencies for running CI tests * All dependencies in `python/*/requirements*.txt` will be pinned to a specific version These version pins should be managed by dependabot in the future. Additionally, this PR resolves the requirements overwriting issue in our current Docker installs. Signed-off-by: Kai Fricke kai@anyscale.com Co-authored-by: Sihan Wang <sihanwang41@gmail.com>
2022-10-19 17:41:09 -07:00
# You can obtain this list from the ray.egg-info/requires.txt
[RLlib] Atari gym environments now require ale-py. (#28703)
2022-09-22 19:05:54 +02:00
## setup.py install_requires
[Core] Remove add_command_alias (#58719) `add_command_alias` deepcopy the `Command` object but it's no longer deep-copyable: https://github.com/pallets/click/issues/3065#issuecomment-3309192371. We can remove it completely since it just creates some command aliases that have been deprecated for 5+ years. Closes #56747 --------- Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com>
2025-11-18 07:36:01 -08:00
click>=7.0
[Core] Add ray[adag] option to pip install (#47009) Add ray[adag] option to pip install
2024-08-14 13:31:13 -07:00
cupy-cuda12x; sys_platform != 'darwin'
*: Centralize requirements.txt and unify dependency versions (#9759) * python_test: fix cython_examples in doc/ and tests/ * update setup.py to parse the bazel version string better * all: centralize all python deps into stackable requirements files in python/ * format * Move cython test into the proper package * Add cross-reference dependency comments for requirements and setup.py * re-enable version pinning on CI, fix formatting * fix up torchvision version * fix case in shell
2020-07-30 11:22:56 -07:00
filelock
Update requirements.txt from setup.py (#36255) The requirements.txt was not kept in sync with changes in setup.py. This PR updates the requirements.txt to match the latest setup.py requirements. Signed-off-by: Kai Fricke <kai@anyscale.com>
2023-06-13 17:03:42 +01:00
jsonschema
[docker] Fix requirements files and installation in docker images (#29375) Requirements installation is currently broken by a glob: The `python/requirements/data_processing/requirements.txt` overwrites the `python/requirements.txt` in a glob copy operation. This leads the docker images to have faulty and incompatible dependencies installed. This PR refactors the requirements management in Ray. In short: * the `python/requirements.txt` will only contain constraints defined in `setup.py` * A new `python/requirements_test.txt` will contain _pinned_ dependencies for running CI tests * All dependencies in `python/*/requirements*.txt` will be pinned to a specific version These version pins should be managed by dependabot in the future. Additionally, this PR resolves the requirements overwriting issue in our current Docker installs. Signed-off-by: Kai Fricke kai@anyscale.com Co-authored-by: Sihan Wang <sihanwang41@gmail.com>
2022-10-19 17:41:09 -07:00
msgpack<2.0.0,>=1.0.0
[llm] upgrade vllm to 0.12.0 (#58026) Related prs that we should review when upgrading fully: - https://github.com/ray-project/ray/pull/58820 - Note from Rui: When we bump new vllm version, we should go with 0.11.2 instead of 0.11.1, which fixes a Ray multi-node PP regression that was introduced when adding torch-based PP https://github.com/vllm-project/vllm/releases/tag/v0.11.2 Issues: - closes https://github.com/ray-project/ray/issues/58937 - closes https://github.com/ray-project/ray/issues/58973 - closes https://github.com/ray-project/ray/issues/58702 --------- Signed-off-by: Kourosh Hakhamaneshi <Kourosh@anyscale.com> Signed-off-by: Seiji Eicher <seiji@anyscale.com> Signed-off-by: Nikhil Ghosh <nikhil@anyscale.com> Signed-off-by: Nikhil G <nrghosh@users.noreply.github.com> Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com> Co-authored-by: Seiji Eicher <seiji@anyscale.com> Co-authored-by: Nikhil Ghosh <nikhil@anyscale.com> Co-authored-by: Nikhil G <nrghosh@users.noreply.github.com> Co-authored-by: elliot-barn <elliot.barnwell@anyscale.com>
2025-12-08 12:23:21 -08:00
packaging>=24.2
[Build][Bugfix] Fix protobuf version (#54910) This pr fixes the `AttributeError: 'str' object has no attribute 'DESCRIPTOR'` when packaging message to dict using `protobuf` Closes #54849 Signed-off-by: MengqingCao <cmq0113@163.com> Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com>
2025-08-12 01:59:59 +08:00
protobuf>=3.20.3
*: Centralize requirements.txt and unify dependency versions (#9759) * python_test: fix cython_examples in doc/ and tests/ * update setup.py to parse the bazel version string better * all: centralize all python deps into stackable requirements files in python/ * format * Move cython test into the proper package * Add cross-reference dependency comments for requirements and setup.py * re-enable version pinning on CI, fix formatting * fix up torchvision version * fix case in shell
2020-07-30 11:22:56 -07:00
pyyaml
requests
Add `--reload` flag to the `serve run` subcommand (#38389) I have implemented a custom watch using the `watchfiles` package, formerly named `watchgod`, for my own local development of Ray Serve applications. It would be nice if this functionality existed in the `serve` Command Line Interface (CLI). I have searched the GitHub issues and Ray forums. This feature has been requested off and on several times. This PR adds the `--reload` flag to the `serve run` subcommand. It will listen for file changes in the specified working directory and redeploy the application. This is similar uvicorn and other web frameworks. It is useful for application development. The `watchfiles` package is added to the `requirements.txt` file and the `setup.py` file as indicated. Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com> Co-authored-by: Christopher Field <chris.field@theiascientific.com>
2023-08-23 08:55:15 -07:00
watchfiles
*: Centralize requirements.txt and unify dependency versions (#9759) * python_test: fix cython_examples in doc/ and tests/ * update setup.py to parse the bazel version string better * all: centralize all python deps into stackable requirements files in python/ * format * Move cython test into the proper package * Add cross-reference dependency comments for requirements and setup.py * re-enable version pinning on CI, fix formatting * fix up torchvision version * fix case in shell
2020-07-30 11:22:56 -07:00
[docker] Fix requirements files and installation in docker images (#29375) Requirements installation is currently broken by a glob: The `python/requirements/data_processing/requirements.txt` overwrites the `python/requirements.txt` in a glob copy operation. This leads the docker images to have faulty and incompatible dependencies installed. This PR refactors the requirements management in Ray. In short: * the `python/requirements.txt` will only contain constraints defined in `setup.py` * A new `python/requirements_test.txt` will contain _pinned_ dependencies for running CI tests * All dependencies in `python/*/requirements*.txt` will be pinned to a specific version These version pins should be managed by dependabot in the future. Additionally, this PR resolves the requirements overwriting issue in our current Docker installs. Signed-off-by: Kai Fricke kai@anyscale.com Co-authored-by: Sihan Wang <sihanwang41@gmail.com>
2022-10-19 17:41:09 -07:00
# Python version-specific requirements
[wheel] declare wheel python version as python 3.10+ (#59835) and remove python dependency requirements for python 3.9 or below Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
2026-01-04 12:27:19 -08:00
grpcio>=1.42.0
[ci] fixes grpcio requirements difference (#55245) sync with the definition in the wheel fixes #55241 Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
2025-08-05 15:14:20 -07:00
[Data] Bump min version of PyArrow from 6.0 to 9.0 (#47040) Dropping Ray Data internal support for Arrow < 9.0.0 as of Ray 2.39. This is necessary in avoiding over-compensating for issues resolved in old Arrow versions, like the ones surfacing in #48266.
2024-11-01 16:44:35 -07:00
pyarrow >= 9.0.0
Update requirements.txt from setup.py (#36255) The requirements.txt was not kept in sync with changes in setup.py. This PR updates the requirements.txt to match the latest setup.py requirements. Signed-off-by: Kai Fricke <kai@anyscale.com>
2023-06-13 17:03:42 +01:00
[docker] Fix requirements files and installation in docker images (#29375) Requirements installation is currently broken by a glob: The `python/requirements/data_processing/requirements.txt` overwrites the `python/requirements.txt` in a glob copy operation. This leads the docker images to have faulty and incompatible dependencies installed. This PR refactors the requirements management in Ray. In short: * the `python/requirements.txt` will only contain constraints defined in `setup.py` * A new `python/requirements_test.txt` will contain _pinned_ dependencies for running CI tests * All dependencies in `python/*/requirements*.txt` will be pinned to a specific version These version pins should be managed by dependabot in the future. Additionally, this PR resolves the requirements overwriting issue in our current Docker installs. Signed-off-by: Kai Fricke kai@anyscale.com Co-authored-by: Sihan Wang <sihanwang41@gmail.com>
2022-10-19 17:41:09 -07:00
# ray[all]
Update requirements.txt from setup.py (#36255) The requirements.txt was not kept in sync with changes in setup.py. This PR updates the requirements.txt to match the latest setup.py requirements. Signed-off-by: Kai Fricke <kai@anyscale.com>
2023-06-13 17:03:42 +01:00
smart_open
lz4
numpy>=1.20
aiorwlock
scipy
colorful
[docker] Fix requirements files and installation in docker images (#29375) Requirements installation is currently broken by a glob: The `python/requirements/data_processing/requirements.txt` overwrites the `python/requirements.txt` in a glob copy operation. This leads the docker images to have faulty and incompatible dependencies installed. This PR refactors the requirements management in Ray. In short: * the `python/requirements.txt` will only contain constraints defined in `setup.py` * A new `python/requirements_test.txt` will contain _pinned_ dependencies for running CI tests * All dependencies in `python/*/requirements*.txt` will be pinned to a specific version These version pins should be managed by dependabot in the future. Additionally, this PR resolves the requirements overwriting issue in our current Docker installs. Signed-off-by: Kai Fricke kai@anyscale.com Co-authored-by: Sihan Wang <sihanwang41@gmail.com>
2022-10-19 17:41:09 -07:00
rich
[core] upgrade opentelemetry-sdk (#53745) This PR updates the `opentelemetry-sdk` version requirement to a minimum of 1.30, which is necessary to support histogram metrics as part of our migration from OpenCensus to OpenTelemetry. As part of this upgrade, I am also removing `opentelemetry-exporter-otlp` from the `ray[all]` dependency set. This package has been notoriously difficult to resolve alongside other dependencies, and this issue becomes even bigger with the updated SDK version. Since it is only used for the Ray tracing feature, I propose making it an optional, user-controlled dependency instead of a default one. Additionally, the test environment has been updated to ensure `test_tracing.py` continues to pass, verifying that tracing functionality remains intact. Test: - CI Signed-off-by: can <can@anyscale.com>
2025-07-09 17:16:29 -07:00
opentelemetry-sdk>=1.30.0
opentelemetry-api
[core][telemetry/01] migrate python telemetry recorder to opentelemetry (#53098) This is a series of PR to migrate metric collection from opencencus to openlemetry. For context, ray has two main parts that instrument and record metric through opencencus: c++ and python part. The python part consists of three components: - A singleton python object (let's call it the TelemetryMetricRecorder) that stores all telemetry that got sent to it in memories. - A PrometheusServer that holds this TelemetryMetricRecorder object. The server takes a snapshot of this object, convert telemetries into prometheus metrics and persist the metrics every few seconds. - A DashboardAgent, which runs as a cronjob on every ray node, that collects node-level telemetries and send them to the TelemetryMetricRecorder The c++ part consists of one component (to be deep dived more): - A cronjob runs on every ray worker and send telemetries to TelemetryMetricRecorder via grpc messages. ---- This PR migrates the TelemetryMetricRecorder from using opencencus to opentelemetry. The migration is also control via a flag (which turns on the new stuff by default). Fairly small PR (most files are auto-generated). Test: - CI + new unit test - test_metrics_agent.py + test_reporter.py has a lot of e2e tests and they still work - e2e test in anyscale (go/cantel01) --------- Signed-off-by: can <can@anyscale.com>
2025-05-27 14:20:43 -07:00
opentelemetry-exporter-prometheus
[core] upgrade opentelemetry-sdk (#53745) This PR updates the `opentelemetry-sdk` version requirement to a minimum of 1.30, which is necessary to support histogram metrics as part of our migration from OpenCensus to OpenTelemetry. As part of this upgrade, I am also removing `opentelemetry-exporter-otlp` from the `ray[all]` dependency set. This package has been notoriously difficult to resolve alongside other dependencies, and this issue becomes even bigger with the updated SDK version. Since it is only used for the Ray tracing feature, I propose making it an optional, user-controlled dependency instead of a default one. Additionally, the test environment has been updated to ensure `test_tracing.py` continues to pass, verifying that tracing functionality remains intact. Test: - CI Signed-off-by: can <can@anyscale.com>
2025-07-09 17:16:29 -07:00
opentelemetry-proto
[serve] Unpin `fastapi` version (#43058) FastAPI has fixed the broken starlette interaction in 0.109.2: https://fastapi.tiangolo.com/release-notes/#01092 Starlette handling of root_path has changed in 0.33.0: encode/starlette#2352. Prior to this, it was incorrectly stripping the root_path from the path field (which we need to mirror). Added compatibility logic to handle both of these. --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Co-authored-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com>
2024-02-12 14:19:12 -06:00
fastapi
[rllib] add ormsgpack in python/requirements.txt (#59730) to be consistent with setup.py; also unpins the version, which allows library users to use newer versions. also relaxes ormsgpack's version so that library users can upgrade it. Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
2025-12-29 22:24:39 -08:00
ormsgpack>=1.7.0
[wheel] declare wheel python version as python 3.10+ (#59835) and remove python dependency requirements for python 3.9 or below Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
2026-01-04 12:27:19 -08:00
gymnasium==1.2.2
[virtual env] release the conda version constraints (#41540) * release version mismatch * [core][usage] Fix autoscaler v2 usage reporting (#41516) --------- Signed-off-by: rickyyx <rickyx@anyscale.com> * [Data] Fix metrics reporting for `torch_batch_inference` release tests (#41451) Followup to #39889, add an option to include additional metrics from Benchmark.run_fn() which do not exactly conform to standard metrics defined in BenchmarkMetrics class. This allows us to report additional metrics originally included in the torch_batch_inference related release tests, and fixes the metrics reporting issue. --------- Signed-off-by: Scott Lee <sjl@anyscale.com> --------- Signed-off-by: rickyyx <rickyx@anyscale.com> Signed-off-by: Scott Lee <sjl@anyscale.com> Co-authored-by: Ricky Xu <xuchen727@hotmail.com> Co-authored-by: Scott Lee <scottjlee@users.noreply.github.com> Co-authored-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com>
2023-12-14 09:37:06 -08:00
virtualenv!=20.21.1,>=20.0.24
[docker] Fix requirements files and installation in docker images (#29375) Requirements installation is currently broken by a glob: The `python/requirements/data_processing/requirements.txt` overwrites the `python/requirements.txt` in a glob copy operation. This leads the docker images to have faulty and incompatible dependencies installed. This PR refactors the requirements management in Ray. In short: * the `python/requirements.txt` will only contain constraints defined in `setup.py` * A new `python/requirements_test.txt` will contain _pinned_ dependencies for running CI tests * All dependencies in `python/*/requirements*.txt` will be pinned to a specific version These version pins should be managed by dependabot in the future. Additionally, this PR resolves the requirements overwriting issue in our current Docker installs. Signed-off-by: Kai Fricke kai@anyscale.com Co-authored-by: Sihan Wang <sihanwang41@gmail.com>
2022-10-19 17:41:09 -07:00
opencensus
Update requirements.txt from setup.py (#36255) The requirements.txt was not kept in sync with changes in setup.py. This PR updates the requirements.txt to match the latest setup.py requirements. Signed-off-by: Kai Fricke <kai@anyscale.com>
2023-06-13 17:03:42 +01:00
aiohttp_cors
*: Centralize requirements.txt and unify dependency versions (#9759) * python_test: fix cython_examples in doc/ and tests/ * update setup.py to parse the bazel version string better * all: centralize all python deps into stackable requirements files in python/ * format * Move cython test into the proper package * Add cross-reference dependency comments for requirements and setup.py * re-enable version pinning on CI, fix formatting * fix up torchvision version * fix case in shell
2020-07-30 11:22:56 -07:00
dm_tree
Update requirements.txt from setup.py (#36255) The requirements.txt was not kept in sync with changes in setup.py. This PR updates the requirements.txt to match the latest setup.py requirements. Signed-off-by: Kai Fricke <kai@anyscale.com>
2023-06-13 17:03:42 +01:00
uvicorn
prometheus_client>=0.7.1
[Data] Cap pandas to <3 for ray[data] and make SettingWithCopyWarning handling pandas-3-safe (#60406)
2026-02-25 00:35:48 +08:00
pandas>=1.3
[ci][7up/3] initial dependency upgrades (#42104) Upgrade ray dependencies to versions that are available on both python 3.9 and python 3.11. ray 3.8 is no longer build-able with these new versions. All tests passed except for two ml tests which the team has agreed to deprecate them w00t w00t. Signed-off-by: can <can@anyscale.com>
2024-03-14 13:37:42 -07:00
tensorboardX
[deps] upgrading aiohttp v3.13.3 (#60231) setting lower bounds for aiohttp v3.13.3 due to security vulnerabilities on previous versions also upgrading aiosignal to 1.4.0 due to the new aiohttp version Open issue: https://github.com/ray-project/ray/issues/59943 Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com> Co-authored-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com>
2026-01-16 20:47:42 -08:00
aiohttp>=3.13.3
[docker] Fix requirements files and installation in docker images (#29375) Requirements installation is currently broken by a glob: The `python/requirements/data_processing/requirements.txt` overwrites the `python/requirements.txt` in a glob copy operation. This leads the docker images to have faulty and incompatible dependencies installed. This PR refactors the requirements management in Ray. In short: * the `python/requirements.txt` will only contain constraints defined in `setup.py` * A new `python/requirements_test.txt` will contain _pinned_ dependencies for running CI tests * All dependencies in `python/*/requirements*.txt` will be pinned to a specific version These version pins should be managed by dependabot in the future. Additionally, this PR resolves the requirements overwriting issue in our current Docker installs. Signed-off-by: Kai Fricke kai@anyscale.com Co-authored-by: Sihan Wang <sihanwang41@gmail.com>
2022-10-19 17:41:09 -07:00
starlette
typer
Update requirements.txt from setup.py (#36255) The requirements.txt was not kept in sync with changes in setup.py. This PR updates the requirements.txt to match the latest setup.py requirements. Signed-off-by: Kai Fricke <kai@anyscale.com>
2023-06-13 17:03:42 +01:00
fsspec
[llm] upgrade vllm to 0.12.0 (#58026) Related prs that we should review when upgrading fully: - https://github.com/ray-project/ray/pull/58820 - Note from Rui: When we bump new vllm version, we should go with 0.11.2 instead of 0.11.1, which fixes a Ray multi-node PP regression that was introduced when adding torch-based PP https://github.com/vllm-project/vllm/releases/tag/v0.11.2 Issues: - closes https://github.com/ray-project/ray/issues/58937 - closes https://github.com/ray-project/ray/issues/58973 - closes https://github.com/ray-project/ray/issues/58702 --------- Signed-off-by: Kourosh Hakhamaneshi <Kourosh@anyscale.com> Signed-off-by: Seiji Eicher <seiji@anyscale.com> Signed-off-by: Nikhil Ghosh <nikhil@anyscale.com> Signed-off-by: Nikhil G <nrghosh@users.noreply.github.com> Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com> Co-authored-by: Seiji Eicher <seiji@anyscale.com> Co-authored-by: Nikhil Ghosh <nikhil@anyscale.com> Co-authored-by: Nikhil G <nrghosh@users.noreply.github.com> Co-authored-by: elliot-barn <elliot.barnwell@anyscale.com>
2025-12-08 12:23:21 -08:00
pydantic!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,!=2.9.*,!=2.10.*,!=2.11.*,<3 # Serve users can use pydantic<2
Upgrade py-spy to 0.4.0 for py312 support (#48978) py-spy 0.4.0 has support for python 3.12. --------- Signed-off-by: Alan Guo <aguo@anyscale.com>
2024-12-04 11:51:07 -08:00
py-spy>=0.2.0; python_version < '3.12'
py-spy>=0.4.0; python_version >= '3.12'
[dashboard] add memray to requirements.txt again (#44401) #44315 is reverted since windows tests are failing. The reason is that memray does not support windows so the pip requirements is failed to run. This PR fixed the requirements issue by conditional install memray when current system platform is not win32 Note: In last PR, we added memray as a required dependency for dashboard (default), and it's not set required in this PR. --------- Signed-off-by: bhuang <bhuang@anyscale.com>
2024-04-03 15:19:14 -07:00
memray; sys_platform != "win32" # memray is not supported on Windows
[Serve] add dependencies on openssl (#47738) Add `pyOpenSSL` dependency for Serve. And update test docker file to use ray[serve-grpc] dependencies. Signed-off-by: Gene Su <e870252314@gmail.com>
2024-09-23 15:07:44 -07:00
pyOpenSSL
add support for async inference (#54824) This PR aims to provide basic support for asynchronous inference in the ray serve. RFC can be found at: https://github.com/ray-project/ray/issues/54652 The PR doesn't contains all the implementation pieces as having all the code changes in a single PR would be very difficult to review. Missing pieces are - implementation of failed and unprocessed task queue for the celery task processor - add more detailed and thorough tests for the same. These missing pieces will be taken care of in the subsequent PRs. --------- Signed-off-by: harshit <harshit@anyscale.com>
2025-08-14 10:21:53 +05:30
celery
[serve] add taskiq dependency (#61054) - we are now introducing the implementation of Taskiq task processor just similar to Celery, we need the `taskiq` dependency in the `serve-async-inference` extra. - for the testing purpose, since we want to test the taskiq with actual redis in the e2e, added the `taskiq-redis` in the `serve-requirements.txt` which seems to be using only in the serve ci tests. Signed-off-by: harshit <harshit@anyscale.com>
2026-02-14 03:11:09 +05:30
taskiq
Reference in New Issue Copy Permalink