|
From: SourceForge.net <no...@so...> - 2012-12-21 00:43:52
|
Bugs item #3597875, was opened at 2012-12-20 11:53 Message generated for change (Settings changed) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3597875&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: com Group: None >Status: Deleted >Resolution: Duplicate Priority: 5 Private: No Submitted By: Kevin Smyth () Assigned to: Nobody/Anonymous (nobody) Summary: pythoncomloader.dll and undefined LoadLibraryEx behavior Initial Comment: MSDN's documentation for LoadLibraryEx states "The behavior is undefined when LOAD_WITH_ALTERED_SEARCH_PATHflag is set, and lpFileName specifiies a relative path." com/win32com/src/PythonCOMLoader.cpp: HMODULE hpycom = LoadLibraryEx(DLL_DELEGATE, NULL, LOAD_WITH_ALTERED_SEARCH_PATH); setup.py: ccargs.append('/DDLL_DELEGATE=\\"pythoncom%s.dll\\"' % (suffix,)) An absolute path should be used instead. ---------------------------------------------------------------------- Comment By: Kevin Smyth () Date: 2012-12-20 12:16 Message: On Windows 7, this undefined behavior seems to result in the standard dll search order. So if pythoncom27.dll isn't on the %PATH%, in System32, in the exe's directory, or in the current working directory (some machines), the LoadLibraryEx call fails. I'm running into this when pywin32 is installed into a virtual env. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3597875&group_id=78018 |
