Python 3.15 introduces lazy imports, and the lazy import object exposes a `resolve()` method that manually triggers reification — returning the actual module object. Calling `resolve()` does not automatically reassign the name in `globals()`, suggesting the Python machinery does something like `globals()[name] = globals()[name].resolve()` when a lazy import is first accessed. The post also notes the open question of what exactly triggers automatic reification when code 'touches' a lazy import.
Sort: