DEV Community

Marinho
Marinho

Posted on

Pynsights — The Python Workshop Manual

Here is a scenario you probably know.

You have been writing Python for a couple of years. You know the language. You can ship features, debug prod issues, maybe even mentor juniors. But somewhere along the way you hit a wall. You hear about the GIL and how it kills performance, but nobody explains why it exists or when it actually matters. You know dicts are fast, but you don't know why they are fast or why they started preserving insertion order in 3.7. You write async code because FastAPI told you to, but when something blocks the event loop you have no mental model for what broke or how to fix it.

So you go looking. You buy an "advanced Python" course. And you feel cheated, because it is just the same basics with fancier words. A user guide pretending to be a workshop manual.

That is the problem Pynsights exists to solve.

Think of most Python resources like a cooking show. They show you the finished dish. They tell you the ingredients. They make it look easy. But they never show you what happens when the knife slips or the pan overheats or the emulsion breaks. They never explain why baking soda works or what heat does to protein at the molecular level. You walk away able to repeat the recipe but unable to cook on your own.

Pynsights is the opposite. It is the kitchen counter where you get flour on your hands and learn why bread rises.

Every topic has three layers of depth. First, a whiteboard with hand drawn diagrams that walk you through the concept like a study session with someone who actually understands it. Second, a step through simulation that shows exactly what the runtime does, instruction by instruction, no black boxes. Third, a written guide with direct links to the official Python docs, the relevant PEPs, and the CPython source code on GitHub. Not paraphrased. Not reinterpreted. The actual source.

If you want to know how dict probing works, you can watch a simulation walk through each probe step. If you want to see the actual C code that does it, the link is right there. If you want to verify the benchmark numbers, the Python script that generated them is in the repository.

This matters because Python is a deceptively deep language. The surface is friendly and productive. But underneath, there are hash tables with perturbed probing, compact dict layouts that save 58% memory, a GIL that has been evolving for thirty years, an async model that is neither threads nor callbacks but something in between, and a bytecode engine that keeps getting faster through adaptive optimization. If you understand these mechanisms, you stop guessing. You start choosing data structures, concurrency models, and API designs that match how the runtime actually works. Your code gets faster, safer, and more predictable.

The project covers 27 topics across sequences, the language model, data structures, memory, classes, async, concurrency, and production patterns. It targets Python 3.10 to 3.14, including free threaded CPython and per interpreter GIL. It expects you already know Python, but even if you are earlier in your journey there is value here.

And it is completely free. Open source. Forever. Not a trial. Not a freemium with a paywall for the good stuff. The code is open for anyone to inspect, verify, correct, or improve. That is by design. Knowledge this fundamental should not be locked behind a course you have to buy to discover it is shallow. It should be out there, on the counter, ready for anyone who wants to learn.

pynsights.vercel.app (https://pynsights.vercel.app)

Top comments (0)