[python-win32] Automation breakage with newer versions of win32all

greg Landrum greglandrum at mindspring.com
Thu Jun 26 11:04:32 EDT 2003


[Python2.2.3, Win2K]

Hi,

Yesterday I upgraded from an older version of the win32 extensions (whatever was distributed with an old ActiveState Python 2.2 release) after I switched to python.org Python2.2.3.  When I did that, some of my most used COM client code broke.  I did a bit of playing around with versions of win32all and uncovered the following:

My code works fine with win32all versions: 142, 146 and 148.  It breaks with 150 and 152.  

Here's a traceback of the error:

Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "c:\glandrum\RD\Python\utils\chemdraw.py", line 83, in CDXConvert
    theObjs.SetData(inFormat,inData)
  File "c:\Python22\Lib\site-packages\win32com\gen_py\5F646AAB-3B56-48D2-904C-A8D7989C251x0x7x0.py", line 401, in SetData
    return self._oleobj_.InvokeTypes(21, LCID, 4, (24, 0), ((12, 17), (12, 17), (12, 17), (12, 17), (12, 1)),dataType, resolution, Width, Height, arg4)
pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 5)

The last call from my code (line 83 of CDXConvert) is to the SetData method of a COM object, two strings are passed as arguments.

My question is: is this likely a bug in the newer builds or is it exposing errors in my code that were being corrected/ignored in the older builds?

Thanks,
-greg




More information about the Python-win32 mailing list