import python as mulan_Python子模块：“import as”vs“import”

这在Python Ideas中讨论过，但是import foo.bar as eggs与{}不同。它们生成不一致的字节码。在The root cause is the import cycle. I played around with dis and found the following (I suspect others have already found this but the thread was hard to follow for me initially):>>> dis.dis('import a.b')

1 0 LOAD_CONST 0 (0)

2 LOAD_CONST 1 (None)

4 IMPORT_NAME 0 (a.b)

6 STORE_NAME 1 (a)

8 LOAD_CONST 1 (None)

10 RETURN_VALUE

>>>compared to

^{pr2}$

What this shows is that the implementation of "import a.b" and "import a.b as c" are different. The former calls import('a.b', ...) which returns the module 'a' and stores that in the variable 'a'. In the OP's case, because of the import cycle, while sys.modules['a.b'] exists, module 'a' does not yet have the attribute 'b'. That's the reason that in the latter example, the LOAD_ATTR opcode fails.>>> dis("import sys.path as path")

1 0 LOAD_CONST 0 (0)

3 LOAD_CONST 1 (None)

6 IMPORT_NAME 0 (sys.path)

9 LOAD_ATTR 1 (path)

12 STORE_NAME 1 (path)

15 LOAD_CONST 1 (None)

18 RETURN_VALUEFor "import sys.path as path", the given module name is "sys.path", and the "from list" entry on the stack is None. This fails before it even reaches the LOAD_ATTR line, since "sys.path" isn't an importable module. Changing LOAD_ATTR to IMPORT_FROM would thus have no effect on its behaviour.>>> dis("from sys import path")

1 0 LOAD_CONST 0 (0)

3 LOAD_CONST 1 (('path',))

6 IMPORT_NAME 0 (sys)

9 IMPORT_FROM 1 (path)

12 STORE_NAME 1 (path)

15 POP_TOP

16 LOAD_CONST 2 (None)

19 RETURN_VALUEFor "from sys import path", the given module name is "sys", and the "from list" entry on the stack is a tuple containing the string "path". This works, since "sys" is importable and it has a "path" attribute.

我想你得等3.7版或者换个进口。在