Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #18825
| From | Stefan Behnel <stefan_ml@behnel.de> |
|---|---|
| Subject | Re: open office in another language? |
| Date | 2012-01-11 14:06 +0100 |
| References | <CAOFf2a0RZo=o9r=We=iGUutfNn9SCeJUMn7ZM+hq=o7RoCN1bg@mail.gmail.com> <mailman.4635.1326272939.27778.python-list@python.org> <87hb02y259.fsf@no-fixed-abode.cable.virginmedia.net> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.4643.1326287200.27778.python-list@python.org> (permalink) |
Paul Rudin, 11.01.2012 11:17: > Stefan Behnel writes: >> OOo has been fully scriptable in Python for ages. It even comes with an >> embedded Python runtime for that purpose [...] > > I have dabbled with PyUNO in the past. One issue is that the api seems > rather unpythonic (to me, at least). Sure, UNO wasn't designed for Python. It's mostly a 1:1 mapping of the C++ API. I didn't find anything in a quick web search, but I'm pretty sure the wrapper is auto-generated in some way. But still: it's there, it's usable and it's even object oriented. And I estimate that it's much easier to use from Python than from C++ (which I never tried). If you want something better, feel free to write a pythonic Cython wrapper of the C++ UNO API. May take a while, though, and you'll also have to rewrite the entire UNO documentation to match your new wrapper, so that people can actually start using it effectively. Stefan
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: open office in another language? Stefan Behnel <stefan_ml@behnel.de> - 2012-01-11 10:08 +0100
Re: open office in another language? Paul Rudin <paul.nospam@rudin.co.uk> - 2012-01-11 10:17 +0000
Re: open office in another language? Stefan Behnel <stefan_ml@behnel.de> - 2012-01-11 14:06 +0100
csiph-web