GeezerVison

With -X lazy_imports=all, from .main import TestProgram, main in unittest/__init__.py binds both names lazily. If TestProgram gets resolved first, loading the unittest.main submodule sets unittest.main to the module, and the pending lazy main is lost. unittest.main() then fails with TypeError: 'module' object is not callable.

main is now assigned from TestProgram (the same object unittest.main.main aliases), so it no longer depends on the lazy binding. test_unittest and test_pyrepl (whose only failure was the same unittest.main colorizing check) pass with lazy imports now, so I removed both from Lib/test/lazy_imports_all_exclude.txt.

The underlying problem is in the lazy import machinery, and any package whose __init__ does from .m import T, m hits it. It is closely related to gh-151208, so this only works around it in unittest until the core behavior is decided there.

Fixes #158086

• Issue: JIT: test_unittest fails with -X lazy_imports=all: unittest.main is a module #158086