Dieter Maurer wrote: > Steve Holden <[EMAIL PROTECTED]> writes on Sun, 22 May 2005 09:14:43 -0400: > >>... >>There are some aspects of Python's initialization that are IMHO a bit >>too filesystem-dependent. I mentioned one in >> >> >> http://sourceforge.net/tracker/index.php?func=detail&aid=1116520&group_id=5470&atid=105470 >> >> >>but I'd appreciate further support. Ideally there should be some means >>for hooked import mechanisms to provide answers that are currently >>sought from the filestore. > > > There are such hooks. See e.g. the "meta_path" hooks as > described by PEP 302.
Indeed I have written PEP 302-based code to import from a relational database, but I still don't believe there's any satisfactory way to have [such a hooked import mechanism] be a first-class component of an architecture that specifically requires an os.py to exist in the file store during initialization. I wasn't asking for an import hook mechanism (since I already knew these to exist), but for a way to allow such mechanisms to be the sole import support for certain implementations. regards Steve -- Steve Holden +1 703 861 4237 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ Python Web Programming http://pydish.holdenweb.com/ -- http://mail.python.org/mailman/listinfo/python-list
