Re: new import mechanism and a "small" distribution

Feb. 1, 1999
2:39 p.m.
Gordon McMillan wrote:
Yup :-) Last month, I even argued that the import mechanism could simply be shifted entirely to Python, too, since the overhead of interpreted Python code is minimal next to the parsing, execution, and/or I/O involved with importing. hehe...
If python.exe doesn't find its registry settings, then it assumes a default sys.path (which includes the current directory). Using that, it loads exceptions.py and then site.py. Once site.py loads, then I install the custom import hook so that all future imports will be yanked from py15.pyl. The builtin modules aren't in there, of course, so those fall down the chain to the builtin importer. Cheers, -g -- Greg Stein, http://www.lyra.org/
9521
Age (days ago)
9521
Last active (days ago)
0 comments
1 participants
participants (1)
-
Greg Stein