Mark Hammond <skippy.hamm...@gmail.com> wrote: > >> As far as the system DLLs, last time I checked they do have to > >> be in the system32 directory (or the wow64 version.) But I could be wrong > >> - > >> I didn't play with that very much. If it works without installing system > >> DLLs I'd be curious to know. > > > > Me, too. I'm guessing you need to do this, to be able to have things > > like windows services find them. But I'd sure like confirmation of that. > > I'm planning to incorporate what's necessary in the post-install for my > > package. > > That's correct - stuff like services and COM requires the DLLs in > system32 - however, you can probably see in the post-install script that > if the user selects to install Python itself "just for me" then pywin32 > doesn't try and copy to system32 etc - if Python itself doesn't have its > DLL in system32, pywin32 can't work in those embedded contexts > regardless of what it tries to do...
Mark, my system is a dozen or so Python programs plus a few Windows services implemented in Python. If I set those up to hack the "Path" environment variable appropriately before importing stuff, could I put the three DLLs somewhere else instead of C:\WINDOWS\System32\? Bill _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
