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 Arfrever, brett.cannon, eric.smith, eric.snow, lemburg, ncoghlan, pitrou
Date 2012-04-24.20:25:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335299135.14.0.687406626788.issue14657@psf.upfronthosting.co.za>
In-reply-to
Content
So basically if you are running in a checkout, grab the source file and compile it manually since its location is essentially hard-coded and thus you don't need to care about sys.path and all the other stuff required to do an import, while using the frozen code for when you are running an installed module since you would otherwise need to do the search for importlib's source file to do a load at startup properly.

That's an interesting idea. How do we currently tell that the interpreter is running in a checkout? Is that exposed in any way to Python code?
History
Date User Action Args
2012-04-24 20:25:35brett.cannonsetrecipients: + brett.cannon, lemburg, ncoghlan, pitrou, eric.smith, Arfrever, eric.snow
2012-04-24 20:25:35brett.cannonsetmessageid: <1335299135.14.0.687406626788.issue14657@psf.upfronthosting.co.za>
2012-04-24 20:25:34brett.cannonlinkissue14657 messages
2012-04-24 20:25:34brett.cannoncreate