[core] [3/N] Use uv as package manager

[dentiny]

This PR integrates uv into existing runtime env system, which uses uv to setup environment for better performance.

TODO list:

• Add uv to public documentation

[pcmoritz]

Great progress! Here are two test cases I'm using to try this out:

In [1]: import ray

In [2]: ray.init(runtime_env={"uv": ["emoji"]})
2024-11-06 13:41:00,419	INFO worker.py:1812 -- Started a local Ray instance. View the dashboard at http://127.0.0.1:8265 
Out[2]: RayContext(dashboard_url='127.0.0.1:8265', python_version='3.11.4', ray_version='3.0.0.dev0', ray_commit='{{RAY_COMMIT_SHA}}')

In [3]: @ray.remote
   ...: def f():
   ...:     import emoji
   ...:     return emoji.emojize('Ray and UV is :thumbs_up:')
   ...: 

In [4]: ray.get(f.remote())

In [1]: import ray

In [2]: ray.init(runtime_env={"uv": ["openai-whisper"]})
2024-11-06 13:45:16,284	INFO worker.py:1812 -- Started a local Ray instance. View the dashboard at http://127.0.0.1:8265 
Out[2]: RayContext(dashboard_url='127.0.0.1:8265', python_version='3.11.4', ray_version='3.0.0.dev0', ray_commit='{{RAY_COMMIT_SHA}}')

In [3]: 

In [3]: @ray.remote
   ...: def f():
   ...:     import whisper
   ...:     return str(whisper.load_model("turbo"))
   ...: 

In [4]: ray.get(f.remote())

Currently failing with

ValueError: Local directory /tmp/ray/session_2024-11-06_13-45-15_408387_64642/runtime_resources/uv/fd1fdf03c7d0becce4e97c66770ea43be96743ac for URI uv://fd1fdf03c7d0becce4e97c66770ea43be96743ac does not exist on the cluster. Something may have gone wrong while installing the runtime_env `uv` packages.

(which is probably expected since you marked it as "draft"). Once it is working I'm also happy to test it on workspaces :)

[jjyao]

LG

[jjyao]

Most pip integration test can have a uv counterpart. Consider reusing the tests by using @pytest.mark.parametrize. This also shows people can just change pip to uv and things will just work.

[dentiny]

Yeah I considered that, but choose to rewrite in these reasons:

• (major) uv and pip are not 100% compatible, which means we will have a number of if-else branches
  • For example, we need to add uv-specific tests at the end
  • I've seen a few community discussions on leveraging uv features, I'm afraid the split will become larger and larger
• (major/minor) pip and uv installation process is different: we consider pip installed by default, while have to install uv ourselves, which means, we need to do extra checking for uv
• (minor) Not all the features are implemented for uv for now, so quite a lot of existing pip-based tests will be skipped;

[jjyao]

Last few comments.