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 Trundle, alex, benjamin.peterson, brett.cannon, eric.araujo, eric.snow, ncoghlan, pitrou, vstinner
Date 2012-03-07.19:55:28
SpamBayes Score 0.00036617846
Marked as misclassified No
Message-id <1331150129.5.0.465086875237.issue2377@psf.upfronthosting.co.za>
In-reply-to
Content
The finding/loading code in import.c is purely because of the imp module's public API (e.g. imp.find_module()). I have been waiting to find out if importlib would get bootstrapped before making the current module _imp and then creating an imp.py which handles most of the high-level stuff (e.g. imp.py containing find_module() and have it use importlib). That would let all of that C code go away since I already tie into the low-level C API for C-level import function calls.
History
Date User Action Args
2012-03-07 19:55:29brett.cannonsetrecipients: + brett.cannon, ncoghlan, pitrou, vstinner, benjamin.peterson, eric.araujo, alex, Trundle, eric.snow
2012-03-07 19:55:29brett.cannonsetmessageid: <1331150129.5.0.465086875237.issue2377@psf.upfronthosting.co.za>
2012-03-07 19:55:28brett.cannonlinkissue2377 messages
2012-03-07 19:55:28brett.cannoncreate