Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #34122 > unrolled thread
| Started by | Albert Dengg <albert@fsfe.org> |
|---|---|
| First post | 2012-12-01 14:01 +0100 |
| Last post | 2012-12-01 14:01 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Help accessing COM .dll from Python Albert Dengg <albert@fsfe.org> - 2012-12-01 14:01 +0100
| From | Albert Dengg <albert@fsfe.org> |
|---|---|
| Date | 2012-12-01 14:01 +0100 |
| Subject | Re: Help accessing COM .dll from Python |
| Message-ID | <mailman.401.1354367361.29569.python-list@python.org> |
[Multipart message — attachments visible in raw view] — view raw
On Sat, Dec 01, 2012 at 12:47:57PM +0000, Steve Simmons wrote: > Gunther - Sorry about that, hoping this response comes through as > plain text. > > Chris - Thanks for the translation and the response. Unfortunately, > I don't speak 'C', and I think the learning curve for Python + COM > should be slightly less steep. i've had some some expirience using COM from python with pywin32, which works reasonably well if your interfaces is documented. as for examples beeing excel centric: it does not really matter, you just have to look the real interface you want to use in the documentation of your libary. there are however some pitfalls, espesially with arguments passed by reference: there not the parameter will be modified but you will have a tuple as a return value. albert
Back to top | Article view | comp.lang.python
csiph-web