`uv pip` and `uv venv`: Managing Packages and Isolating Environments

A lot of Python confusion is really location confusion. You install something, but where did it go? You run something, but which environment is it using? That is the knot uv venv and uv pip help untangle.

What `uv venv` does

The notes describe uv venv simply: it creates a virtual environment.

uv venv

A virtual environment gives you an isolated place for Python packages. Isolation matters because it keeps one project’s dependencies from casually spilling into another project’s setup.

Even when the definition is short, the effect is important. A virtual environment changes where later package actions are meant to land.

What `uv pip` is for

The notes describe uv pip as a pip-compatible interface for managing Python packages.

uv pip install requests

This is the part of uv that feels closest to traditional package installation workflows. The actor is uv, the action is package management, and the data being touched is the installed package set for an environment.

Installing and uninstalling packages

The notes include the basic inverse clearly:

uv pip install requests
uv pip uninstall requests

That pair makes it easier to experiment. You can add a package, test whether it belongs, and remove it if it does not.

Why these commands belong together

It is possible to talk about environments and package installation separately, but beginners usually understand both better when they are introduced together.

uv venv answers, “Where should this package live?”

uv pip install answers, “What package should go there?”

Without that pairing, package installation can feel weirdly abstract. With it, the workflow becomes more concrete: create an isolated space, then manage packages inside that space.

A small example workflow

uv venv
uv pip install requests
uv pip uninstall requests

The sequence reads cleanly. First make the isolated environment. Then install a package. Then remove it if needed.

What this is not

This is not the same as uv tool install. When you use uv pip, you are managing packages with a pip-compatible interface. When you use uv tool, you are focused on commands provided by Python packages.

That difference seems subtle until you have to explain why one package should be available as a tool while another should just live inside a project environment.

What to remember

Use uv venv to create isolation. Use uv pip to install or remove packages within that kind of setup. When you are confused, ask where the package is meant to live. That question often clears up the rest.

Raell Dottin's Technical Blog