Topic track
Project Setup & Dependency Management
Build a dependable foundation with packaging, dependency resolution, versioning, virtual environments, and distribution workflows for Python CLI projects.
Content-driven handbook for Python CLI teams
A practical handbook for building, testing, packaging, and shipping production-ready Python command-line applications — more than 180 in-depth guides across four tracks.
Browse the knowledge base
Start with the track that matches the problem in front of you — every guide links up to its section and sideways to related pages.
Topic track
Build a dependable foundation with packaging, dependency resolution, versioning, virtual environments, and distribution workflows for Python CLI projects.
Topic track
Choose frameworks, structure command trees, and design extensible, fast-starting command-line systems that can scale with your product or team.
Topic track
Improve validation, config loading, error handling, logging, and terminal rendering so Python CLIs stay predictable for both humans and automation.
Topic track
Run subprocesses safely, write files atomically, call HTTP APIs, add concurrency, protect credentials and keep long-running commands healthy.
New in this release
Subprocesses, HTTP APIs, secrets, CI/CD, interface design and terminal UIs — what a CLI needs once it works with other systems and other people.
Call git and other tools safely: argument lists instead of shells, timeouts, streamed output and exit codes that mean something.
Build an httpx client with retries and backoff, paginate results, download with progress and log in with the OAuth device flow.
Keep tokens in the OS keyring, prompt without echo, support several profiles and redact secrets from every log line.
Test across Python versions, smoke-test the built wheel, release from git tags and publish to PyPI with trusted publishing.
Consistent names, dry runs for destructive commands, global versus per-command options and the POSIX conventions users expect.
Decide when a command should become a full-screen app, build one with Textual, and test it headlessly with Pilot.
How to use the handbook
Go straight to the guide. Every page opens with the answer before the explanation, so the first screen is usually enough to get unblocked.
Follow the recommended path on each track overview, in order. It front-loads the decisions that are expensive to reverse: layout, locking, and the shape of the command tree.
Run the eight-invocation audit at the end of the input and terminal UX overview. Each failure points at the guide that fixes it.