As a follow-up, a clean install of Windows 7, Python 2.7.6 and pywin32 2.18 in
a Virtual Machine does not exhibit this behavior. The Python extension
actually works in Explorer.
So, it would seem that some other currently installed extension might be
colliding with this. However, I'd still like
Hi Vernon
This system in 32bit XP, so no bitness problems probable.
Regards,
Łukasz
Dnia Tue, 15 Apr 2014 23:14:21 +0200, Vernon D. Cole
napisał:
One other thing to check: are Python and DO11 this same 32 or 64
bit-ness?
32 bit programs cannot talk to 64 bit COM, and vice-versa.
On T
Hello Mark,
This is the output:
# This window will display output from any programs that import
win32traceutil
# win32com servers registered with '--debug' are in this category.
Object with win32trace dispatcher created (object=None)
in 0x05932D90>._InvokeEx_-SetScriptSite(with obj at 0x04B3C
That all looks OK. There is a hack in the axscript engine that means
you may be able to use a prefix of 'ax.' - eg, ax.DOpus.OpenOutputWindow()
HTH,
Mark
On 17/04/2014 5:31 AM, Łukasz Jakubowski wrote:
Hello Mark,
This is the output:
# This window will display output from any programs that
As far as seeing the print statements, you can modify the source file to
have "import win32traceutil" at the top, and in another console run
"python -m win32traceutil" - the print statements from the source file
should them appear in the console running win32traceutil.
However, I don't think t
