I did check add to path. I tried different installations on another system, also Win 7 with Visual Studio 2017 installed (including python). In short ActiveState's 32 bit Python didn't work, but using the pywin32 installer did.
1. ActiveState 32 bit version. It does not update the menus, though it does update the path. Many of the programs won't run. <file>C:\Python36\Lib\site-packages\pythonwin\Pythonwin.exe</file> will not; it says it needs mfc100u.dll. The file is in Windows\SysWOW64; despite the name, this is for 32 bit programs running on 64 bit windows. It does not appear in System32, which is for 64 bit dlls! Pythonwin.exe is actually 64 bit according to a tool I wrote. The package doesn't seem to have been built quite right; I uninstall the package. In fairness the fact that there are at least 2 other pythons installed (both 64 bit and both more recent than the ActiveState I installed) probably makes this a challenging environment. 2. Install Python 3.7 32 bit from python.org and download the pywin32 installer and run. This differs from my previous approach, which used pip to get pywin32. This seems to work; I get new menu entries and can run Pythonwin. Note the Visual Studio associated pythons were both 3.6. The lesson seems to be to use the pywin installer, not pip, to install pywin. Coda: I still have COM problems on the new system because it encounters the same problem as before when the file being registered by COM is on the network share: the call to list the file never returns. This seems to be a Windows 7 thing not a python thing, since FindNextFile keeps returning the same file repeatedly when called from C++; VBA shows the same problem. The problems does not occur from Win Server 2012 R2. Visual Studio 2017 says it targets Windows 10 and has no other options I know of. I doubt that's the problem since python and pywin32 may not have been built with it and VBA in Access 2010 certainly wasn't built with it. Ross ________________________________________ From: python-win32 <python-win32-bounces+ross.boylan=ucsf....@python.org> on behalf of mc@mclaveau <m...@mclaveau.com> Sent: Wednesday, December 19, 2018 12:32:24 AM To: python-win32@python.org Subject: Re: [python-win32] Initial setup and COM debugging issues. Hi! During the installation of python, did you check well to add Python in the PATH? This option is at the very bottom of the frame, and not very visible. @-salutations -- [cid:part1.55697E79.A202DABA@mclaveau.com] Le 18/12/2018 à 20:58, Boylan, Ross a écrit : pywin32 is installed just for me, but python itself is installed for all users. I have C:\Users\rdboylan\AppData\Roaming\Python\Python37\site-packages\pythonwin\Pythonwin.exe but when I try to run it (double-click or command prompt in that directory) I get The application can not locate win32ui.pyd (or Python) (126 That file is in the same folder as Pythonwin.exe. Searching turned up some suggestions this is a 32 vs 64 bit problem; everything should be 32 bit (though 64 bit OS) but I'm not sure how to check. The system itself definitely has both 32 and 64 bit pythons installed. Ross ________________________________________ From: python-win32 <python-win32-bounces+ross.boylan=ucsf....@python.org><mailto:python-win32-bounces+ross.boylan=ucsf....@python.org> on behalf of Dennis Lee Bieber <wlfr...@ix.netcom.com><mailto:wlfr...@ix.netcom.com> Sent: Wednesday, December 12, 2018 11:19:46 AM To: python-win32@python.org<mailto:python-win32@python.org> Subject: Re: [python-win32] Initial setup and COM debugging issues. On Wed, 12 Dec 2018 02:10:36 +0000, "Boylan, Ross" <ross.boy...@ucsf.edu><mailto:ross.boy...@ucsf.edu> declaimed the following: So I think my installation is missing some pieces. I installed the standard Windows version of Python from python.org and used pip to install pywin32. There are a number of different pythons installed on the system. I've always installed ActiveState builds, which include pywin32/win32py (I think the name has changed over its history). To my knowledge PythonWin IDE is included as part of pywin32. Searching suggested the invoked tool was win32traceutil.py; I tried to launch it, but it failed because it had a Python 2 print statement. TraceCollector.py says it is a win32traceutil like utility, so I tried that: C:\Users\rdboylan\AppData\Roaming\Python\Python37\site-packages\pythonwin\pywin\tools>py TraceCollector.py Traceback (most recent call last): I'm guessing you installed Python for single user, given that path. Did you try running the pythonwin executable. Note that the documentation which you trimmed actually states "... for PythonWin" -- which could imply that it is trying to interface with the (expected) pythonwin IDE process -- something you don't have active. I believe all the tools in .../pywin/tools are meant to be invoked by PythonWin itself. PS C:\Users\Wulfraed> Get-ChildItem -Path c:\ -Recurse -Name -Filter "*pythonwin*" Python27\Lib\site-packages\pythonwin Python27\Lib\site-packages\pythonwin\Pythonwin.exe Python35\Lib\site-packages\pythonwin Python35\Lib\site-packages\pythonwin\Pythonwin.exe {Yes, a bit behind -- ActiveState, after all, has to wait for python.org releases before they can start building and testing for their release -- and 3.6, last I looked, is just the core; 3.5 includes a massive number of third party packages} -- Wulfraed Dennis Lee Bieber AF6VN wlfr...@ix.netcom.com<mailto:wlfr...@ix.netcom.com> HTTP://wlfraed.home.netcom.com/ _______________________________________________ python-win32 mailing list python-win32@python.org<mailto:python-win32@python.org> https://mail.python.org/mailman/listinfo/python-win32 _______________________________________________ python-win32 mailing list python-win32@python.org<mailto: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
