Kristján Valur Jónsson added the comment: Like I mentioned on python-dev, it worries me a bit that this could be considered "unexpected", i.e. when there is a conflict between a legitimage attribute member of a module, and a submodule of the same name.
Also, I wonder if this isn't a bigger change to the import mechanism, than simply: | Another would be | to always require an 'as' clause in this case, so that you would have | to write' | import .foo as foo which would possibly only require a change to the syntax. ---------- nosy: +kristjan.jonsson _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17636> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
