It may be that Python 3.15's lazy imports like lazy import some_module evade componentize-py's build-time loading and thus trigger runtime errors.
Hairier still, cycles of lazy imports are allowed, even celebrated as one of lazy imports' motivating use cases. Are those going to cause trouble for us? Should we just continue to recommend explicitly importing them in a place that runs at build time? There exist lazy-import cycles in the stdlib. Are they going to ruin our day?
Now take a deep breath: we're still on 3.14 here.
It may be that Python 3.15's lazy imports like
lazy import some_moduleevade componentize-py's build-time loading and thus trigger runtime errors.Hairier still, cycles of lazy imports are allowed, even celebrated as one of lazy imports' motivating use cases. Are those going to cause trouble for us? Should we just continue to recommend explicitly importing them in a place that runs at build time? There exist lazy-import cycles in the stdlib. Are they going to ruin our day?
Now take a deep breath: we're still on 3.14 here.