On 26/02/2009 3:56 AM, Boris Borcic wrote:
Hello,
I just moved a python ISAPI between servers, the code works fine except
that "import win32traceutil" doesn't work any more for the ISAPI.
On the other hand, "import win32traceutil" in a small test program run
either from the pythonwin environment or with python.exe, works all
right : the pywin "Python Trace Collector" tool shows all printed messages.
Any idea for rectifying this would be welcome.
Pythonwin version : 2.5.4
Possibly relevant : the move was made in the simplest possible manner,
by installing the current (2.5.4) ActivePython for the major version
(2.5) on the target machine and simply copying files not included in the
distribution, even though the ActivePython on the source machine was in
fact 2.5.1, this on the basis of the idea that binary compatibility is
guaranteed between minor versions. Could this be a (the) mistake ?
I believe that build 212 had a problem with win32traceutil, introduced
trying to get things working on Vista. Build 213 should have that
fixed, but on Vista it may be necessary to either (a) run win32traceutil
as an admin or (b) ensure IIS has already imported win32traceutil before
starting the reader process.
Unfortunately I'm not sure what builds of ActivePython correspond to
real pywin32 builds...
Cheers,
Mark
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
