This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients brett.cannon, eric.smith, kaorihinata
Date 2021-03-16.19:51:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for the clarification! I think I understand what's going on now, and the logic is actually expected.

When you do `from .test_submodule import *`, Python must first import `test_pkg.test_submodule` in order to get you the object for the `import *` part (or frankly anything that comes after `import`). As part of importing `test_pkg.test_submodule`, it automatically gets attached to `test_pkg`, otherwise we wouldn't be able to cache the module in `sys.modules` and prevent redundant/duplicate imports.

As such, when you do `import test_pkg` in``, the fact that `test_pkg.__init__` has to import `test_pkg.test_submodule` means `test_pkg will automatically end up with a `test_submodule` attribute. That's why your `print()` function call succeeds.

If I'm still misunderstanding, can you please use an `assert` statement that fails because the logic doesn't work the way you expect it to be?
Date User Action Args
2021-03-16 19:51:34brett.cannonsetrecipients: + brett.cannon, eric.smith, kaorihinata
2021-03-16 19:51:34brett.cannonsetmessageid: <>
2021-03-16 19:51:34brett.cannonlinkissue43477 messages
2021-03-16 19:51:34brett.cannoncreate