About
Python’s packaging and tooling ecosystem earned its reputation for confusion. Official documentation is conservative, fragmented across dozens of projects, and slow to reflect what developers have actually adopted. The Python Developer Tooling Handbook exists because that gap needed filling.
This is a single-author project. It takes clear positions on what tools to use, explains the trade-offs honestly, and covers alternatives with accuracy. The handbook follows the Diataxis framework: tutorials for learning, how-to guides for getting things done, explanations for understanding, and reference pages for looking things up.
About the author
Tim Hopper is an AI research engineer at Spotify and a CPython contributor. Over the past decade, he has built AI/ML platforms, feature stores, and data science infrastructure at companies including Varo Bank, BlackBerry/Cylance, and Distil Networks. He holds a Master’s in Operations Research from NC State.
The handbook grew out of years spent onboarding data scientists and ML engineers onto Python tooling that was harder to learn than it needed to be. Tim started writing the guides he wished existed, and the project became the resource you see today.
Why trust this handbook?
The handbook is independent, ad-free, and maintained as Python tooling changes. Recommendations are based on production use, ecosystem standards, official documentation, and active tracking of packaging and developer-tooling changes.
The handbook focuses on decisions, not catalog entries. It helps Python developers and teams choose tools with enough context to understand the trade-offs. When the handbook recommends a default, it explains why. When an alternative is still worth knowing about, it says where that alternative fits.
Sponsorship helps fund the work, but sponsors do not control recommendations or editorial judgment.
Links
- Resume
- GitHub
- pythonplot.com — a guide to Python plotting libraries
- Into the Hopper — podcast on ML and software engineering