[issue24530] `import..as` fails where `import` does not

R. David Murray added the comment: Ah, yes, that is the issue I was thinking of. So, bug, not doc issue :) -- ___ Python tracker ___

[issue24530] `import..as` fails where `import` does not

Martin Panter added the comment: Maybe Issue 23203, proposing to fix the compiled bytecode. -- nosy: +vadmium resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Aliasing import of sub-{module,package} from the package raises AttributeError on import. _

[issue24530] `import..as` fails where `import` does not

R. David Murray added the comment: I'm pretty sure this has already been reported, but I have no idea how to search for the issue :) If I remember correctly there's a doc patch, so I suppose it hasn't been applied. But I could be misremembering. -- nosy: +brett.cannon, eric.snow, r.d

[issue24530] `import..as` fails where `import` does not

New submission from Dustin J. Mitchell: Reproduction: # main.py import foo.bar # foo/__init__.py # (empty) # foo/bar/__init__.py import foo.bar.bing as bing # foo/bar/bing.py # (empty) Result: dustin@euclid ~/tmp $ python3.3 main.py Traceback (most recent call last): File "main.py", line