pypa.io valid

pipx

pipx installs and runs end-user Python applications in isolated environments. It fills the same role as macOS’s brew, JavaScript’s npx, and Linux’s apt. Under the hood it uses uv when available and pip otherwise, but unlike either it creates a separate virtual environment for each application, so their dependencies never collide and an uninstall leaves nothing behind.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T05:13:22.808Z. Cached copy · Source on pypa.io

# pipx

> pipx installs and runs end-user Python applications in isolated environments. It fills the same role as macOS’s brew, JavaScript’s npx, and Linux’s apt. Under the hood it uses uv when available and pip otherwise, but unlike either it creates a separate virtual environment for each application, so their dependencies never collide and an uninstall leaves nothing behind.

The documentation follows the Diátaxis framework: tutorials to learn pipx by doing, how-to guides for specific tasks, a reference for the CLI and environment, and explanation for how pipx works and how it compares to other tools.

## Start here
- [pipx overview](https://pipx.pypa.io/latest/index.html): pipx installs and runs end-user Python applications in isolated environments. It fills the same role as macOS’s brew, JavaScript’s npx, and Linux’s apt. Under the hood it uses uv when available and pip otherwise, but unlike either it creates a separate virtual environment for each application, so their dependencies never collide and an uninstall leaves nothing behind.
- [Tutorials](https://pipx.pypa.io/latest/tutorial/index.html): Step-by-step lessons that take you from zero to productive with pipx. Start at the top if you are new.
- [How-to guides](https://pipx.pypa.io/latest/how-to/index.html): Task recipes for pipx. Each guide states a goal, walks through the steps, and ends with a check that the change took effect. They assume pipx is already installed unless the guide is about installing it.
- [Reference](https://pipx.pypa.io/latest/reference/index.html): Technical reference for pipx: the command-line interface, environment variables, exit codes, machine-readable output, and on-disk metadata.
- [Explanation](https://pipx.pypa.io/latest/explanation/index.html): Design rationale and background. Read these to understand why pipx works the way it does.

## Tutorials
- [Getting started](https://pipx.pypa.io/latest/tutorial/getting-started.html): This tutorial covers the core pipx workflow: install an application, run it, upgrade it, and remove it. Work through it top to bottom with one small package, and you will know every command you need day to day.
- [Installing applications](https://pipx.pypa.io/latest/tutorial/install-applications.html): getting-started walked through the install → list → run → uninstall cycle with the toy pycowsay package. This tutorial repeats it with a real tool so you can see how a package’s name and its apps differ.
- [Running applications](https://pipx.pypa.io/latest/tutorial/run-applications.html): pipx run downloads and runs a Python application in a one-time, temporary environment, then leaves your system untouched. Reach for it to scaffold a new project, check an app’s help text, or try a tool without committing to an install.

## How-to guides
- [Install pipx](https://pipx.pypa.io/latest/how-to/install-pipx.html): Get pipx onto your system and add its app directory to your PATH.
- [Upgrade pipx](https://pipx.pypa.io/latest/how-to/upgrade-pi
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=pypa.io · GET /v1/domain/pypa.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for pypa.io:
1. POST https://agentwebmap.com/v1/sites/pypa.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://pypa.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/pypa.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/pypa.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.