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.
The message means that no one has defined a meaning for the name DOpus to
Python.
You, as a programmer, must define that name. If you say:
DOpus = Spam and Eggs
then you have defined it as a character string which contains three English
words.
If you say:
from win32com.client import Dispatch
Hi Vernon,
Thanks for the answer.
The DOpus object is not supposed to be created by a user with Dispatch (as
DO11 author has told me) - DO11 has no ProgID to use. The object is
brought into script before passing control to it in the same way as fe.
WScript in case of .pys, by calling
Hi, everybody.
I'm having an issue with the context_menu.py example included with pywin32
(2.18) under Python 2.7.6. I register it by running it (python
context_menu.py --register), but then, when I right-click on a Python file,
my Explorer process terminates. I've tried variations (some
You might like to try using the 32bit builds of python and pywin32.
HTH,
Mark
On 14/04/2014 2:48 AM, Pierre Mallard wrote:
Hello,
I'm running on Windows8.1 64 bits, Excell 2013, Python 3.4 and
pywin32-218.win-amd64-py3.4
That might be a newbee question but I'm running out of idea to fix
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
