On Monday, July 1, 2002, at 08:31 , Oren Tirosh wrote: > Can anyone > explain why Mac/Python/macimport.c is messing with ob_sinterned? It's all explained in the comment a few lines above where ob_sinterned is used: /* ** If we have interning find_module takes care of interning all ** sys.path components. We then keep a record of all sys.path ** components for which GetFInfo has failed (usually because the ** component in question is a folder), and we don't try opening these ** as resource files again. */ This code gives a considerable speedup for module searches. The reason it's mac-specific is that MacPython allows files on sys.path as well as directories (and these files are searched for PYC resources). -- - Jack Jansen <Jack.Jansen@oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -
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