> I suspect this change in Python will dramatically improve the performance of such large programs as well.
Makes packaging super fun too, where you need to hit every possible path so you don't miss anything imported in 1% of the execution paths :)
Or, you could just use a project-level specification file to list dependencies rather than looking for imports in the code, trying to figure out what they resolve to, and trying to package the results.
Can't you do some kind of static analysis instead?
I can't even express how negatively I feel about build/packaging systems that process dependencies based on code-level imports instead of some explicit build manifest separate to the code.