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 eric.snow
Recipients benjamin.peterson, brett.cannon, eric.snow, pjenvey
Date 2012-04-18.05:30:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334727006.21.0.124338259079.issue14609@psf.upfronthosting.co.za>
In-reply-to
Content
_find_and_load() in importlib._bootstrap returns whatever the loader returns, which is the new module object.  The old code in import.c pulled it from sys.modules rather than using what the loader returned.  In both cases the respective object is what eventually gets bound to the name in the eval loop.

FWIW, the language reference says, "The first form of import statement binds the module name in the local namespace to the module object".    This looks like a corner case where backwards-compatibility breaks (when we finally start enforcing the rules).
History
Date User Action Args
2012-04-18 05:30:06eric.snowsetrecipients: + eric.snow, brett.cannon, pjenvey, benjamin.peterson
2012-04-18 05:30:06eric.snowsetmessageid: <1334727006.21.0.124338259079.issue14609@psf.upfronthosting.co.za>
2012-04-18 05:30:05eric.snowlinkissue14609 messages
2012-04-18 05:30:05eric.snowcreate