What is the difference between production and editable installs in uv?

Production installs create a static wheel package (snapshot), while editable installs (--editable) create symlinks to your source code. Use editable mode during active development to see changes immediately.

How do I fix a 'Command not found' error after uv installation?

Verify your pyproject.toml has the correct [project.scripts] entry points defined. After updating the file, perform a clean reinstall by removing build artifacts and running 'uv tool install --force .'.

Why don't my code changes show up after using uv tool install?

This is often caused by a stale build cache. You need to manually remove the build/, dist/, and *.egg-info/ directories, then run 'uv tool install --force .' to ensure a fresh build snapshot is created.

How can I verify which version of a tool is currently running?

Use the command 'which ' to see the executable path. You can also compare the output of 'uv run --version' (local source) against the global command to identify version mismatches.

UV Debugger

Name: UV Debugger
Author: WarrenZhu050413

byWarrenZhu050413

•

Developer Tools

Troubleshoots and resolves Python package management issues when using the uv toolchain.

About

The uv-debug skill provides systematic diagnostic workflows to identify and fix common issues with the uv Python package manager, such as stale build caches, installation discrepancies, and missing modules. It helps developers understand the nuances between production and editable installations while providing clear steps to resolve 'command not found' errors or sync issues. By utilizing this skill, Claude can guide users through cleaning build artifacts, verifying entry points in pyproject.toml, and maintaining a stable Python development environment.

Key Features

Guidance on switching between editable and production installation modes
Validation steps for pyproject.toml entry points and dependencies
5 GitHub stars
Diagnostic workflows for uv tool installation discrepancies
Systematic troubleshooting for stale build artifacts and caches
Automated cleanup commands for build, dist, and egg-info directories

Use Cases

Standardizing clean-and-reinstall workflows for Python CLI tools
Resolving code changes that don't appear after running uv tool install
Fixing ModuleNotFoundError for newly added Python files in a package

About

Key Features

Guidance on switching between editable and production installation modes
Validation steps for pyproject.toml entry points and dependencies
5 GitHub stars
Diagnostic workflows for uv tool installation discrepancies
Systematic troubleshooting for stale build artifacts and caches
Automated cleanup commands for build, dist, and egg-info directories

Use Cases

Standardizing clean-and-reinstall workflows for Python CLI tools
Resolving code changes that don't appear after running uv tool install
Fixing ModuleNotFoundError for newly added Python files in a package