mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-05-14 22:02:59 -07:00
docs(core): refine uv installation methods to align with official docs
- Replace 'pip install uv' with officially recommended standalone installer (curl/powershell) and system package managers (brew). - Update Python tooling guidance to prioritize project conventions before falling back to uv. - Synchronize vitest snapshots.
This commit is contained in:
File diff suppressed because it is too large
Load Diff
@@ -227,7 +227,7 @@ Use the following guidelines to optimize your search and read patterns.
|
||||
|
||||
<examples>
|
||||
- **Initial Reconnaissance & Testing:** Run ONE command to gather project context and environment constraints: \`find . -name "*test*" -type f -exec cat {} +; uname -a; command -v uv python3 gcc\`.
|
||||
- **Python Tooling:** Proactively check for established project conventions (e.g., \`poetry\`, \`hatch\`, \`pdm\`). If such a tool is used, prefer it. Otherwise, prefer \`uv\` for high-performance environment management (\`uv run\`, \`uv pip\`). If \`uv\` is missing and no other convention exists, proactively attempt to install it (e.g., via \`pip install uv\` or system package manager) if the environment allows; otherwise, fall back to standard \`python3\` and \`pip\`.
|
||||
- **Python Tooling:** Proactively check for established project conventions (e.g., \`poetry\`, \`hatch\`, \`pdm\`). If such a tool is used, prefer it. Otherwise, prefer \`uv\` for high-performance environment management (\`uv run\`, \`uv pip\`). If \`uv\` is missing and no other convention exists, proactively attempt to install it using officially recommended methods (e.g., \`curl -LsSf https://astral.sh/uv/install.sh | sh\` on macOS/Linux, \`brew install uv\`, or standalone installers) if the environment allows; otherwise, fall back to standard \`python3\` and \`pip\`.
|
||||
- **Searching:** utilize search tools like ${GREP_TOOL_NAME} and ${GLOB_TOOL_NAME} with a conservative result count (\`${GREP_PARAM_TOTAL_MAX_MATCHES}\`) and a narrow scope (\`${GREP_PARAM_INCLUDE_PATTERN}\` and \`${GREP_PARAM_EXCLUDE_PATTERN}\` parameters).
|
||||
- **Searching and editing:** utilize search tools like ${GREP_TOOL_NAME} with a conservative result count and a narrow scope. Use \`${GREP_PARAM_CONTEXT}\`, \`${GREP_PARAM_BEFORE}\`, and/or \`${GREP_PARAM_AFTER}\` to request enough context to avoid the need to read the file before editing matches.
|
||||
- **Understanding:** minimize turns needed to understand a file. It's most efficient to read small files in their entirety.
|
||||
|
||||
Reference in New Issue
Block a user