[python-win32] Possible trouble with pywin23-216 on python 3.2

[Mark Hammond]

On 3/03/2011 4:15 PM, Vernon Cole wrote:
> Attempting to install using the binary installer, the installer gets to
> "postinstall script finished", but the display window says:
> v v v v v v v v
> Copied pythoncom32.dll to C:\Windows\system32\pythoncom32.dll
> Copied pythoncomloader32.dll to C:\Windows\system32\pythoncomloader32.dll
> Copied pywintypes32.dll to C:\Windows\system32\pywintypes32.dll
> FAILED to register the Python COM objects
> -> Software\Python\PythonCore\3.2\Help[None]=None
> -> Software\Python\PythonCore\3.2\Help\Pythonwin
> Reference[None]='C:\\Python32\\Lib\\site-packages\\PyWin32.chm'
> Pythonwin has been registered in context menu
> Shortcut for Pythonwin created
> Shortcut to documentation created
> Traceback (most recent call last):
>    File "<string>", line 372, in install
>    File "<string>", line 170, in RegisterCOMObjects
>    File "C:\Python32\lib\site-packages\win32com\server\register.py", line 47
>      except win32api.error, (code, fn, msg):
>                           ^
> SyntaxError: invalid syntax
> Traceback (most recent call last):
>    File "<string>", line 604, in <module>
>    File "<string>", line 471, in install
>    File "C:\Python32\lib\site-packages\win32com\client\__init__.py",
> line 424
>      except pythoncom.com_error, details:
>                                ^
> SyntaxError: invalid syntax
> ^ ^ ^ ^ ^ ^
>
> When the adodbapi test is run, it gives:
> v v v v v v
> C:\hg\adodbapi\testP3k>c:\python32\python.exe testadodbapi.py
> Traceback (most recent call last):
>    File "testadodbapi.py", line 28, in <module>
>      import win32com.client
>    File "c:\python32\lib\site-packages\win32com\client\__init__.py",
> line 424
>      except pythoncom.com_error, details:
>                                ^
> SyntaxError: invalid syntax
> ^ ^ ^ ^ ^ ^ ^ ^ ^
> Which sounds oddly familiar.
> This is on Windows Vista Home Basic.

*sob* - I tested 3.2 with a 64bit build and didn't perform a test 
install of the 3.2 32bit exe.  The 64bit one is fine and I don't 
understand how that could have happened - in theory the 2 builds share 
the same .py files - but it has happened :(

I'll check 3.1 tomorrow and try to determine what went wrong in the 
build process, then put up new builds where necessary...

Thanks,

Mark