@@ -1367,16 +1367,16 @@ The Python ``import`` machinery separates out finding a module and loading
13671367it, and the lazy import implementation could technically defer only the
13681368loading part. However:
13691369
1370- - Finding the module does not guarantee the import will succeed, nor even
1371- that it will not raise ImportError.
1372- - Finding modules in packages requires that those packages are loaded, so
1373- it would only help with lazy loading one level of a package hierarchy.
1374- - Since "finding" attributes in modules *requires * loading them, this would
1375- create a hard to explain difference between
1376- ``from package import module `` and ``from module import function ``.
1377- - A significant part of the performance win is skipping the finding part
1378- (which may involve filesystem searches and consulting multiple importers
1379- and meta-importers).
1370+ - Finding the module does not guarantee the import will succeed, nor even
1371+ that it will not raise ImportError.
1372+ - Finding modules in packages requires that those packages are loaded, so
1373+ it would only help with lazy loading one level of a package hierarchy.
1374+ - Since "finding" attributes in modules *requires * loading them, this would
1375+ create a hard to explain difference between
1376+ ``from package import module `` and ``from module import function ``.
1377+ - A significant part of the performance win is skipping the finding part
1378+ (which may involve filesystem searches and consulting multiple importers
1379+ and meta-importers).
13801380
13811381Placing the ``lazy `` keyword in the middle of from imports
13821382----------------------------------------------------------
0 commit comments