Marc-Andre Lemburg <m...@egenix.com> added the comment: Brett Cannon wrote: > > Brett Cannon <br...@python.org> added the comment: > > 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.
Right. > 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? There's some magic happening in site.py for checkouts, but I'm not sure whether any of that is persistent or even available at the time these particular imports would happen. Then again, I'm not sure you need to know whether you have a checkout or not. You just need some flag to identify whether you want the search for external module code to take place or not. sys.flags could be used for that. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14657> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
