win32com/makepy question

[Tom Willis]

Just a general question.

It seems in COM late binding is something that should be avoided if possible.

Because python seems to be really good at doing thing dynamically I'm
wondering why no one has figured out how to make the functionality in
makepy fire automagically when you need it.

For example, it would be nice if you are creating an object
repeatedly(ADOD B.Recordset) that some logic would trigger whatever
makepy does to generate and cache the modules generated from the
typelib that's accessed.


It would be cool, that's all I'm saying. I'm sure the standard
response is "Why don't you write it" and maybe I will, I'm just
wondering if anyone has thought of it before and is working on it or
whatever.


--
Thomas G. Willis

http://paperbackmusic.net

[Robert Kaplan]

Re: win32com/makepy question


Hi,

I've been looking at the client side com stuff in __init__.py in the
client subdirectory under win32com, and some of the routines do exactly
that. Certainly DispatchWithEve nts tries to generate that, and I
thought Dispatch does before returning a late binding object.

Hope this helps,

Bob


Tom Willis wrote:
[color=blue]
>Just a general question.
>
>It seems in COM late binding is something that should be avoided if possible.
>
>Because python seems to be really good at doing thing dynamically I'm
>wondering why no one has figured out how to make the functionality in
>makepy fire automagically when you need it.
>
>For example, it would be nice if you are creating an object
>repeatedly(ADO DB.Recordset) that some logic would trigger whatever
>makepy does to generate and cache the modules generated from the
>typelib that's accessed.
>
>
>It would be cool, that's all I'm saying. I'm sure the standard
>response is "Why don't you write it" and maybe I will, I'm just
>wondering if anyone has thought of it before and is working on it or
>whatever.
>
>
>
>[/color]