A curated, non-exhaustive support map
This is a map of named tested subsets, not a promise that every program in a feature family works. Current Python standards and the current breadth declaration own the full evolving scope.
Implemented: named tested subsets
The displayed PEP 526 fixture proves annotated assignment with an initializer (doubled: int = ...) and a bare annotation without an initializer (total: int). Its separate registered conformance test checks debug and release builds; those builds are not the displayed debug run.
Current-tree update, separate from the historical hero: In the module prologue, from __future__ import annotations is accepted as a compile-time no-op and binds no feature name. The PEP 563 subset proves that this directive leaves supported own-class method annotations and already-defined-class function annotations working. Later-defined forward references, string annotations, and runtime __annotations__ introspection remain unsupported. This is partial evidence, not whole-PEP acceptance. See the directive contract and divergences, production CLI tests, and three proven categories and three core gaps. The separate PEP 563 fixture was observed green across all five Tier-1 targets in debug and release on main CI run 33972731538. This update does not extend the PEP 526 transcript's evidence.
Partial: core gaps remain
PEP 526 remains a subset row (◐), not whole-PEP acceptance (D-177). The fixture does not prove parenthesized annotated targets, module- and class-level __annotations__ recording, or annotated attribute and subscript targets. The current declaration classifies all three as core gaps. Its explanatory reasons are not a second frozen implementation claim here.
Experimental
No separately accepted experimental language hero is established by this evidence.
Not yet supported
General union annotations and arbitrary container representations are outside the current implemented subset. Native container support is restricted to list[int], dict[str, int], set[int], and scalar tuples; Optional is limited to int, float, and bool. A green subset fixture does not remove these boundaries. Broader compatibility, CPython interop, and incremental compilation remain roadmap work.
Permanent non-goals are different from missing implementation: dynamic eval/exec, monkey-patching, and runtime class creation are rejected by design. Consult the rejected-by-design list. Planned syntax is not a runnable quick start.
Keep the evidence in context
Read language support and its limits, exact compiler diagnostics, current implementation status, and the compiler architecture. The current roadmap describes evolving scope; links labeled current may advance beyond this historical run.