[python-win32] Initial setup and COM debugging issues.

[Boylan, Ross]

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.edu at python.org> on behalf of Dennis Lee Bieber <wlfraed at ix.netcom.com>
Sent: Wednesday, December 12, 2018 11:19:46 AM
To: python-win32 at python.org
Subject: Re: [python-win32] Initial setup and COM debugging issues.

On Wed, 12 Dec 2018 02:10:36 +0000, "Boylan, Ross" <Ross.Boylan at 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
        wlfraed at ix.netcom.com    HTTP://wlfraed.home.netcom.com/

_______________________________________________
python-win32 mailing list
python-win32 at python.org
https://mail.python.org/mailman/listinfo/python-win32