Open dougransom opened 4 months ago
"Installing globally Outside of a virtual environment you might want to install COM objects, services, etc. You can do this by executing:
python Scripts/pywin32_postinstall.py -install From the root of your Python installation.
If you do this with normal permissions it will be global for your user (a few files will be copied to the root of your Python install and some changes made to HKCU). If you execute this from an elevated process, it will be global for the machine (files will be copied to System32, HKLM will be changed, etc)"
I will test but we don't need to have it globally as admin but per user for python virtual environment.
LexiconCode, could you, at least the explanation of Doug, include this issue in a problems section of your Natlink documentation?
Thanks, Quintijn
If this happens during post_install script of pywin32 or during python running (ie within natlink) then From https://pypi.org/project/pywin32/
In almost all cases, this tends to mean there are other pywin32 DLLs installed in your system, but in a different location than the new ones.
.Most likely if this happens, there are old pythons kicking around with pywin32 installed.
Note this error can happen in dragon, but perhaps not in other python environments, because it seems to be random which set of pywin32 dlls are picked up. So your command line tests might work fine. Or vice versa.
It is recent that pywin32 is a prerequisite for natlink (via dtactions). Unimacro required pywin32 since time immemorial.