PEP 810: Explicit lazy imports

[ferdnyc (FeRD (Frank Dana))]

@kapinga

Put another way: library authors already have no control over when their module is imported.

@kapinga

Thus: if your module has special requirements about when it can be imported, it’s already incumbent on you to clearly document these to consuming code. The only thing that would change is to include consideration of lazy imports into that documentation.

And the chance of causing unexpected problems when attempting to enforce those requirements programmatically is high enough to make such enforcement a bad idea, IMHO. Like how calling sys.exit(1) when user code imports an “internal-use only module” that’s not meant to be imported directly may seem like a good idea, but it crashes pydoc -k scans.