You could try registering the python engine for debugging - change to
win32comext/axscript/client and run "python pyscript.py --debug" - a
message should be printed that the object is registered for debugging.
Then, run "python -m win32traceutil" - this will run a python program
where debug statements should end up. Then run your script and examine
the output - hopefully you will see the names of objects created - it
may simply be a case issue.
HTH,
Mark
On 16/04/2014 3:17 AM, Łukasz Jakubowski wrote:
Hello,
I have a problem with a file manager called Directory Opus 11. It
supports ActiveScripting languages, but in case of python, its global
objects are not visible in global namespace.
Python packages (python-3.4.0, pywin32-218.win32-py3.4) seem to be
installed correctly (fe. WScript object is visible in .pys scripts), and
ActiveScripting engine is actually called by Directory Opus.
Where should I start debugging? Are there some possible flags not set or
attributes not presented by the Directory Opus objects that could be
checked? Any namespaces to be searched?
The exact error message is as follows:
DOpus.OpenOutputWindow()
^
Traceback (most recent call last):
File "<Script Block >", line 6, in <module>
DOpus.OpenOutputWindow()
NameError: name 'DOpus' is not defined
(0x80020009)
TIA & Regards,
Łukasz
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
