Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment:
The problem is caused by the "import logging" in bar/__init__.py, which causes bar.logging to not be found because it clashes with the stdlib logging package. If you change the statement to from . import logging then the error does not occur. So I don't think it is a bug, because it is caused by using a module name which is part of the stdlib in an ambiguous way. ---------- nosy: +vinay.sajip type: crash -> behavior _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44120> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
