On Sun, Feb 28, 2010 at 11:07:27PM +1000, Nick Coghlan wrote: > Michael Foord wrote: > >> Can't it look for a .py file in the source directory first (1st stat)? > >> When it's there check for the .pyc in the cache directory (2nd stat, > >> magic number encoded in filename), if it's not check for .pyc in the > >> source directory (2nd stat + read for magic number check). Or am I > >> missing a subtlety? > > > > The problem is doing this little dance for every path on sys.path. > > To unpack this a little bit for those not quite as familiar with the > import system (and to make it clear for my own benefit!): for a > top-level module/package, each path on sys.path needs to be eliminated > as a possible location before the interpreter can move on to check the > next path in the list. Aha, that was the clue I was missing. Thanks! Floris -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4