[issue39637] Probably incorrect message after failed import

Change by Rick van Rein : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue39637] Probably incorrect message after failed import

Rick van Rein added the comment: Thanks for explaining. It is indeed confusing, even though I'm quite experienced with Python. -- ___ Python tracker ___

[issue39637] Probably incorrect message after failed import

Steven D'Aprano added the comment: > Shouldn't that say that "'environ' is not a package" instead? No. The os module is special, so I'll talk about the usual case first. Normally, for `import spam.eggs` to succeed, *spam* has to be a package, and *eggs* has to be either a sub-module inside

[issue39637] Probably incorrect message after failed import

New submission from Rick van Rein : The following error message surprises me: >>> import os.environ Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'os.environ'; 'os' is not a package Shouldn't that say that "'environ' is not a package" instead?