"Schollnick, Benjamin" <[EMAIL PROTECTED]> writes: >> > It's okay.... I just miss McMillian's installer... >> > It's unsupported, so I've moved to py2exe... But >> > McMillian's package seemed to be better with >> > the dependency issues.... And offered a few >> > features that don't exist in py2exe... (Or at least >> > are not easily handled in py2exe...) >> > >> > On the plus side, py2exe has handled packages lately >> > that I just could not get McMillian's installer >> > to work reliably with... Which is why I switched... >> >> I always wondered why no one picked up McMillan and continued >> to develop or at least maintain it - it's open source after >> all, isn't it? > > Yes... It was... > > In my case, I never was motivated, and I suspect it's got > quite complex code behind it... > > Py2exe is a good replacement... I'm generally happy, there's > only a few issues that I have not been able to solve. > > For example, making a plugin based, expandable, generic > build.py.... If I do, the typlibs that I attempt to import > die... > > Plus right now, I have solved the LsaLookupNames2 issue, but > it appears that I need different typelibs between W2000 & WinXp. > But here I am on a development XP system, and can't generate the > ones for 2000.... (Yes this isn't py2exe's fault... But....)
(Should I change the subject, again, to py2exe ? ;-) We recently had this issue with wmi, which also needs different typelibs on XP and 2K, maybe you can look up the thread. Since Tim was only using the typelib wrapper to access some constants, it was possible to avoid the typelib at all by using some code I posted to find the constants at runtime. The best solution, imo, would be to let the frozen exe create the wrapper at runtime if it is not found in the exe - but this may require some nontrivial pywin32 hacking. Thomas _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
