Reading bytecode without cargo culting it
Use disassembly as versioned evidence, connect stack operations to source semantics, and avoid turning CPython opcodes into false contracts.
Independent field notes / Vol. 01
Precise explanations of the machinery, patterns, and tradeoffs that make Python feel deceptively simple.
Read the cover storyThe index
49 notes, edited for signal.
Use disassembly as versioned evidence, connect stack operations to source semantics, and avoid turning CPython opcodes into false contracts.
Hash tables for membership, uniqueness, algebra, and the costs sets deliberately trade away.
Understand slotted storage, descriptors, inheritance, weak references, and when measured memory savings justify the constraints.
Inspect how CPython 3.14 adapts hot bytecode to stable runtime types, and where it cannot help.
Code points, compact representations, allocation behavior, and the boundaries where text becomes bytes.
Use typing protocols, ABCs, and capability checks without confusing static compatibility with runtime proof.
Trace module identity, partial initialization, reloads, and cache invalidation through Python's real import protocol.
Use structured concurrency to make child lifetime, sibling cancellation, and multiple failures explicit.
Editorial policy
No listicles. No folklore. No just trust me abstractions.
Every note should leave you with a better model of the system, not just another snippet to paste.