We're building a new production server for one of our systems, and 
thought it would be a good time to bump up that system from Python 2.4 
to 2.5.  Problem is, the web server, running under the machine's system 
account, can't see the registered COM libraries we've hooked in with the 
MakePy tool.  After much hair pulling, we noticed that when we run 
MakePy on the servers running AS Python 2.4, the generated modules are 
dropped right into the 
<python-installation> lib\site-packages\win32com\gen_py directory, 
whereas on the new machine, running AS Python 2.5, the modules are built 
in the current user's %TEMP% directory, so of course the web server 
can't find them.

So, two questions.

 1. Why the change?
 2. What do we need to do to make the generated modules available to any 
account on the system?

Thanks!

-- 
Bob Kline
http://www.rksystems.com
mailto:bkline@[...].com

_______________________________________________
ActivePython mailing list
ActivePython@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/ActivePython