On the Mac I've introduced "magic cookies" into sys.path, which allow you to do interesting searches (like searching for a DLL or PYC-resource in the application itself) at known places in the import process. There isn't a cookie for "search along the standard MacOS dll search path" (which is somewhat similar to the Windows dll search path) because I haven't seen a reason for it, but there's nothing to stop it. And if you'd insert that cookie it would be perfectly clear (at least, it should be) that only dll modules will be found in that step, not .py modules. Actually I'm so happy with the magic cookie scheme that I've advocated at various times in the past that something similar also be used for determining where builtin modules and frozen modules appear in sys.path... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
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