Allocation is work: object churn and memory locality
Measure temporary objects, retained memory, and data layout before trading clarity for reuse.
Independent field notes / Vol. 01
Precise explanations of the machinery, patterns, and tradeoffs that make Python feel deceptively simple.
Read the cover storyThe index
29 notes, edited for signal.
Measure temporary objects, retained memory, and data layout before trading clarity for reuse.
Follow one dotted expression through instance state, class namespaces, descriptors, method binding, and fallback hooks.
Diagnose circular imports as order-sensitive access to incomplete module namespaces, then repair the dependency graph instead of shuffling lines.
Understand late binding, shared nonlocal state, loop callbacks, and the CPython cells underneath lexical closures.
Follow Python source through ASTs and code objects, then watch execution supply the frame and namespaces that compiled code does not contain.
Replace the parent-call myth with a precise model of MRO-relative lookup, cooperative methods, and safe multiple inheritance.
Connect Python allocations to pymalloc arenas, pools, blocks, process RSS, tracemalloc domains, and responsible measurement.
Move useful work across Python, native, I/O, and process boundaries without optimizing the wrong crossing.
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.