[python-win32] Re: Can we add 'native COM support' to a 3rd p arty DLL/OLB

[Thomas Heller]

Andrew MacIntyre <Andrew.MacIntyre at aba.gov.au> writes:

> > From: Andrew MacIntyre 
> > Sent: Monday, 26 May 2003 5:36 PM
> 
> {...}
> 
> > While it would be nice to be able to use Pythonwin & ctypes together, 
> > as far as I can make out there's no way to get a useful IUnknown 
> > pointer (to feed to ctypes) from Pythonwin's PyIUnknown objects.
> 
> You only see these things afterwards... ;-|
> 
> The repr() of a PyIUnknown:
> <PyIUnknown at 0x10a182c with obj at 0xe7924c>
>                                      ^^^^^^^^
> 
> Just parsing the repr() output should get an address for the object.
> I'll experiment a bit more tomorrow...

Sounds hackish ;-), but if it works...

> 
> BTW, I've encountered a couple of problems with the readtlb.py generated 
> interface files:
>  - a considerable number of out-of-order class definitions (I expect 
>    this is in the source .olb file, and not much you can do; I mention 
>    it in case someone else trips over it...);

Are these for Structures/Unions?

>  - there is one class in this particular object library that starts with 
>    2 underscores - this causes a puzzling name error!;

Should be fixed in readtlb, I guess

>  - there was a pointer definition that didn't get made, though I can see 
>    it in an IDL file generated from the same object library.

and this one also.

> 
> I'm still wading through the re-ordering of this interface file (!3500 
> class defs, ~40000 lines)...

Sounds this is too much be be reordered manually.

Maybe you can mail me the tlb file or, less useful, the generated
py-file by private mail so I can look into this?

Thomas