On Tue, 8 Jan 2002, Trent Mick wrote: > > There is one odd discrepancy between the (newer) problem machine and the > > development machine for sys.path: on the development machine the second > > element (c:\winnt\system32) is not present. Removing it does not > > eliminate the slow module loading, though. > > Off topic because you said that that does not affec the loading time > but: I don't know what c:\winnt\system32 should be there. It is not > in my Python installation so it is not a std Python (or > ActivePython) thing. Look in > HLKM/Software/Python/PythonCore/X.X/PythonPath/. Do any of the > entries under that registry keys include "c:\winnt\system32"?
No, although .../PythonCore/2.0/Modules/(pythoncom|pywintypes) both have paths for DLLs in C:\Winnt\System32. That's true of the development machine as well, though, where c:\winnt\system32 doesn't show up in sys.path. -- Bob Kline mailto:[EMAIL PROTECTED] http://www.rksystems.com _______________________________________________ ActivePython mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/activepython
