publishing-python-packages
Examples and exercises for Publishing Python Packages from Manning Books 🐍 📦 ⬆️
The companion repo for Publishing Python Packages
The book ships its source as a template you copy and work through. Each chapter keeps its examples in its own directory, and the README points at the contribution guidelines for anything that looks wrong.
What this repo is for
The repository description ties the contents to Publishing Python Packages, a Manning title, and calls them examples and exercises. The README says the source code for the book's examples and exercises lives here, and the repository is set up as a template, so a reader can make their own copy and follow along with the printed chapters. Nothing in the project tries to stand alone as a library; the material exists to support the book.
How the chapters are arranged
Each chapter's examples get their own directory. Some chapters hold several snippets inside a single module, and those snippets will not always produce output when you run them; a few exist purely to demonstrate a concept. Later chapters hand some modules the job of entrypoint for a command line program, importing other modules along the way. The README is direct about this: follow along in the book for the context these files assume.
Errata and questions
The errata note is short. If you find a mistake in the code or in the book, or you have a question about the content, the README sends you to the contribution guidelines before you take any other step. Errors that turn up after the book has been printed will be published on the book's homepage, which the repository's metadata links to as pypackages.com.
The project at a glance
The project is Python, licensed under MIT, with a homepage pointed at pypackages.com. It was created in August 2021 and last touched in March 2026. GitHub's counters show 100 stars, 32 forks, and a single open issue. Those are modest numbers for a companion exercise repo, but the README never promises activity or usage, only the supporting code for the book.
Editorial conclusion
Readers get a workbench, not a product. You copy the template, run the chapters, and route problems through the contribution guidelines, with printed-book errata landing on the homepage. The repo claims nothing beyond the book.
Community notes