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 Aaron.Meurer, Ronan.Lamy, brett.cannon
Date 2012-05-28.21:28:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338240499.2.0.77584928307.issue14938@psf.upfronthosting.co.za>
In-reply-to
Content
You can't have it both ways. If you explicitly import __init__ then it becomes just another module to Python, but you still need the implicit package module (i.e. without the __init__ name) for everything else to work since so much of the import system relies on the name of the module itself. If one chooses to work around the import system by doing stuff that is non-standard you will get quirky results like this.

Closing as "won't fix" as it isn't worth the code complication to support such an edge case.
History
Date User Action Args
2012-05-28 21:28:19brett.cannonsetrecipients: + brett.cannon, Aaron.Meurer, Ronan.Lamy
2012-05-28 21:28:19brett.cannonsetmessageid: <1338240499.2.0.77584928307.issue14938@psf.upfronthosting.co.za>
2012-05-28 21:28:18brett.cannonlinkissue14938 messages
2012-05-28 21:28:18brett.cannoncreate