Over the course of this discussion, the term for who should have control over the -L setting was simplified from:
to just “application developer”, which is, IMO, the wrong one of the two.
As an example, the developers of the application black don’t pin versions of their dependencies, so they have no control over the kind of details that might make lazy imports fail.
It seems to me that many deployments of black don’t have an integrator – that is, someone who pins the versions and runs the tests to ensure everything works (and potentially patches in some set_eager_imports calls).
More generally, I’m worried real-world experience is from a very specific deployment, which affects a lot of the PEP’s claims, from debuggability to the performance numbers.
Sadly, I don’t have a suggestion how to make this better, short of implementing it and letting people play with it.
(I’m speaking for myself only, other members of the Steering Council might disagree with me)