On 12/10/2011 02:24, Mark Hammond wrote: > I just pushed a change which introduces a new win32com.client.VARIANT > object. This object can be used in some situations to control the specific > types passed as parameters to COM objects and should address a relatively > common problem people hit when COM objects are very picky about the types > they accept. > > I'm purposely being a little vague in this message about how it works to > encourage people to check out the new documentation and see if it makes > sense and describes how and when it can be useful. The docs are at > http://pywin32.hg.sourceforge.net/hgweb/pywin32/pywin32/raw-file/36b16bcc5c9a/com/win32com/HTML/variant.html > (and will obviously be included in the help file in future builds) > > If anyone has any general comments or comments on the documentation, I'm all > ears! I hope to release a new pywin32 within a few weeks with this feature, > but if anyone has a specific usecase they would like to test it out on, > please contact me privately with the version of Python you are using and > I'll make a test build available. > > Thanks, > > Mark > > Small typo in the docs, the text refers to 'DumpDispatch' in one place rather than 'DumbDispatch.
I think this feature is great, the use case I run across most often is the last one mentioned, where the IDL specifies a VARIANT parameter but the COM object is actually much more picky about the accepted types. OPC suffers a fair bit from this, as the implementation quality of OPC servers varies a lot. -- Regards, Graham Bloice _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
