Free-threaded CPython, immortal objects, per-interpreter GIL, JIT work, stable ABI design tradeoffs, import system edge cases, serialization internals, security boundaries, and future directions.
| Chapter | Title |
|---|---|
| 92 | Free-Threaded CPython |
| 93 | Immortal Objects |
| 94 | Per-Interpreter GIL |
| 95 | JIT Work in CPython |
| 96 | Stable ABI Design Tradeoffs |
| 97 | Import System Edge Cases |
| 98 | Serialization Internals |
| 99 | Security Boundaries |
| 100 | Future Directions |
92. Free-Threaded CPythonPEP 703 no-GIL build: per-object locking, biased reference counting, and the free-threaded evaluation loop.
93. Immortal ObjectsPEP 683 immortal objects: _Py_IMMORTAL_REFCNT sentinel, zero-cost incref/decref, and implications for forks.
94. Per-Interpreter GILPEP 684 per-interpreter GIL: isolated interpreter state, shared-nothing model, and module isolation requirements.
95. JIT Work in CPythonCPython 3.13 copy-and-patch JIT: template JIT design, trace selection, and the roadmap toward full JIT compilation.
96. Stable ABI Design TradeoffsWhat breaking the stable ABI costs, historical breakages, versioning policy, and the tradeoff against new features.
97. Import System Edge CasesCircular import resolution, namespace package search order, zip imports, and __import__ hook edge cases.
98. Serialization Internalspickle protocol versions, the __reduce__ / __reduce_ex__ protocol, marshal format, and shelve internals.
99. Security BoundariesCPython security model: what is and is not sandboxed, restricted execution limits, and audit hook coverage.
100. Future DirectionsActive PEPs, the free-threaded and JIT roadmaps, memory model work, and how to follow CPython development.