Test Python 3.15 lazy imports before moving application startup work
A top-level import is often doing more work than its caller needs. A command-line program may import an optional client, a report renderer, or an SDK before it has parsed the subcommand that would use it. That work is visible as startup latency, but moving imports into functions can make dependency ownership difficult to see and can postpone errors in ways that are hard to test.
Python 3.15 adds explicit lazy imports through PEP 810. A lazy import statement keeps the normal, module-level declaration but defers loading the named module until code uses it. That makes it useful for a narrow startup boundary, not a switch to apply across an application without tests. An import that registers a plugin, changes process state, reads configuration, or is needed to make a module importable has an observable time boundary. Moving that boundary can change behavior even when the imported module itself is correct.