docs: add instructions to install uv

[biswapanda]

Overview:

add instructions to install uv

Summary by CodeRabbit

• Documentation
  • Expanded setup instructions to include installing uv and creating/activating a “dynamo” Python virtual environment.
  • Added a clear link to the uv installation guide and copy‑pasteable commands for environment setup.
  • Standardized the virtual environment name (“dynamo”) for consistency across the README.
  • Updated both “Create a Python virtual env” sections to reflect the new steps and ensure parity between duplicated instructions.

[coderabbitai]

Walkthrough

README.md is updated to add explicit uv installation and virtual environment setup steps. The instructions are inserted in both "Create a Python virtual env" sections, using a "dynamo" environment name and showing an installation via astral.sh with "url" instead of "curl".

Changes

Cohort / File(s)	Summary of Changes
Docs: README updates README.md	Added uv installation and venv setup steps in two sections. Uses astral.sh install command shown with "url" and creates/activates a "dynamo" virtual environment with uv venv dynamo and source dynamo/bin/activate.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• docs: Refactor README.md and add components/README.md #2141 — Also modifies README installation instructions, overlapping with new uv and venv guidance in this PR.

Poem

I hopped through docs with nimble cheer,
Dropped “uv” crumbs for all to hear.
A “dynamo” burrow, warm and bright,
Activate, and code takes flight.
curl? or url? I twitch an ear—
Ready to venv, the path is clear! 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

README.md (1)

258-266: Avoid duplicating uv installation instructions in multiple places.

This section repeats installation steps already shown in “Initial setup” above. To keep docs DRY and easier to maintain, consider either:

• Linking back to the earlier section (“See Initial setup for installing uv”) and only showing the venv creation/activation here, or
• Extracting a small “Installing uv” subsection once and referencing it where needed.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between fb10ffb and 35b77ce.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

README.md

260-260: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build and Test - dynamo

🔇 Additional comments (1)

README.md (1)

258-259: Good call-out to the official uv installation guide.

Linking to the upstream install docs reduces drift as uv evolves. Looks good as-is.