[Docs] use uv in GPU installation docs

[davidxia]

for consistency since uv is now recommended instead of pip for this project.

Put existing pip install commands into collapsed sections.

Slack thread

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Summary of Changes

Hello @davidxia, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the GPU installation documentation to consistently recommend and use uv instead of pip for installing vLLM and its dependencies. This change ensures that the documentation reflects the project's current best practices and provides users with the most up-to-date installation instructions.

Highlights

• Documentation Update: Replaced instances of pip with uv pip in the GPU installation documentation to align with the project's recommendation of using uv for package management.
• Installation Instructions: Updated the installation instructions for pre-built wheels, latest code, specific revisions, and building from source to use uv pip instead of pip.
• PyTorch Installation: Modified the instructions for using an existing PyTorch installation to recommend uv pip for installing PyTorch nightly builds.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the GPU installation documentation to consistently use uv instead of pip. I've identified a potential issue with the updated commands for installing nightly PyTorch builds, which could lead to installation failures, and a suggestion to improve the documentation regarding ccache.

[hmellor]

I'm fine with reducing the complexity of the document by removing dedicated pip/uv sections. But I think we should keep some of the more important information about using pip in collapsed admonitions.

For example

```bash
uv pip install -U vllm \
    --torch-backend=auto \
    --extra-index-url https://wheels.vllm.ai/nightly
```

??? console "pip"
    ```bash
    pip install -U vllm \
        --pre \
        --extra-index-url https://wheels.vllm.ai/nightly
    ```

    `--pre` is required for `pip` to consider pre-released versions.

The reason to do this is that developers might have their own preference for Python package manager, so if we provide them with the pip commands, they can use them to figure out what their commands should be (in a way that would be harder if we only provide the uv commands)

[davidxia]

I'm fine with reducing the complexity of the document by removing dedicated pip/uv sections. But I think we should keep some of the more important information about using pip in collapsed admonitions.

Good point! Added all the important pip parts back as collapsed admonitions. Ready for another review.

[hmellor]

Thanks for making those changes (sorry it took so long to get back to this PR).

I agree with Gemini's comment about the aarch64 command.

[davidxia]

@hmellor No worries. Thanks, applied Gemini's suggested edit in 5d46322.

[hmellor]

LGTM thanks!