Michael Eddington schrieb:
> First, thanks for comtypes :)
You're welcome, and thanks for moving the question to the mailing list.
> I'm curious what the roadmap looks like for stabilizing the interfaces.
>
> The comtypes interface has been changing release to release creating a
> need to rewrite portions of code that use comtypes for later releases
> and creating version hell for end users (like me).
Which interfaces do you mean, exactly?
> If the interface is going to be in flux for sometime it would be great
> to allow multiple versions of comtypes to be installed at once
> allowing different modules or apps to use the version they understand.
> Currently I'm porting a few modules I use to a common version of
> comtypes which is a less then optimal solution.
You CAN install comtypes with easy_install as egg, in multi-version mode
(or how it is called). That way, you have to write
import setuptools; setuptools.require("comtypes==0.3.4")
or something like that before importing comtypes.
> If I can help facilitate this by slinging some code let me know.
Of course it helps to test the releases and provide feedback.
The roadmap / TODO list that I have in mind:
(A remark before: In our company we use an internal upstream version of comtypes
to connect to ATL-written COM servers, and we use ATL to connect to
comtypes implemented COM servers. Quite a lot. But we do not use
dispinterfaces,
only custom or dual interfaces. So dynamic dispatch support in comtypes is
currently
weak.)
1. Fix all the bugs that you guys find, of course. Most of them probably come
because you users will use comtypes to interface servers that are normally
thought to be driven by VB, or use dynamic dispatch.
2. Complete the safearray code. Currently VT_UNKNOWN and VT_DISPATCH
typecodes ate not supported. The safearray code can unpack multidimensional
safearray, but not pack them. I'm unsure how important packing multidim
safearrays
is, I'm also unsure whether they should be packed from nested Python lists
(win32com
supports that), ot if maybe numpy arrays should be accepted. Personally, I
currently
do NOT have the need for multidim arrays.
3. The upstream comtypes version contains much better COM server support.
I would like to integrate these changes, but the interface must stabilize first.
I fear these changes may have some impact on how the COM events code must be
written.
Thomas
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
comtypes-users mailing list
comtypes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/comtypes-users
