[python-win32] VARIANT type not supported error

[Greg Antal]

Mark:

Thanks for the confirmation, and thanks for the fix.

- Greg Antal

Gregory W. Antal
Senior Technical Advisor
ATA Engineering, Inc.
11995 El Camino Real, Suite 200	
San Diego, CA  92130
www.ata-e.com

greg.antal at ata-e.com
858-480-2072  (Phone)
858-792-8932  (Fax)



Mark Hammond wrote, On 6/12/2009 12:49 AM:
> On 11/06/2009 11:24 AM, Greg Antal wrote:
>> Greetings, Experts:
>>
>> I've run into this error and wonder if any of you can help.
>>
>> First I get this message:
>> [snip]\lib\site-packages\win32com\client\__init__.py:480:
>> RuntimeWarning: tp_compare didn't return -1 or -2 for exception
>> elif type(obj)==TupleType:
>>
>> Something then raises an exception (NOT a pythoncom.com_error), from
>> which I extract this traceback, exception type, and value:
>> [snip]
>> iRet, nOpen, liOpen = zFem.feAppGetAllModels ()
>> In feAppGetAllModels, "PyFemap.py" line 14661,
>> , nModelID)
>> In _ApplyTypes_, "__init__.py" line 449,
>> user, resultCLSID)
>> In _get_good_object_, "__init__.py" line 467,
>> return _get_good_object_(obj, obUserName, resultCLSID)
>> In _get_good_object_, "__init__.py" line 480,
>> elif type(obj)==TupleType:
>>
>> <type 'exceptions.TypeError'>- The VARIANT type 0x14 is not supported
>> for SAFEARRAYS
>
> I think the "noise" before this error was already fixed, but yeah, 
> there isn't support in pythoncom for 64bit ints - mainly as the SDK 
> header files indicate they aren't value.  However, the MIDL compiler 
> accepts them, so I just checked in a fix for this.  Unfortunately 
> though, this means you need to wait for the next build, or build it 
> yourself from CVS.
>
> Cheers,
>
> Mark