On Wed, 2014-02-19 at 11:42 -0500, Kevin Hunter Kesling wrote:
I'm sorry to have ignited a discussion for which I wasn't looking. I
clearly don't have the authority to weigh in given my (lack of)
meritocratic wealth in the LibO community, so let me keep this simple:
I'm truly just trying to find an agreeable avenue for hacking on LibO
given my use cases and time.
Hi Kevin,
Just to be clear, I do see PyUNO as a very important part of LibreOffice
as the product, which can potentially be a major selling point over MS
Office which still uses Visual Basic as the main macro language. And I
do see that it's a shame that we don't have enough documentation
coverage on PyUNO, and I'm all for increasing the stability of PyUNO.
I was just trying to point out some of the mis-understandings
surrounding the test framework and some practical view points from those
of us who are in the front line. But then the discussion has blown out
of proportion and we are now basically discussing the origin of the
universe...
So, please don't feel bad about this.
Hopefully what Stephan has proposed is a good starting point for you?
There are places for Python tests, which nobody is disputing.
Kohei
Context
- Re: Testing/Working on PyUNO? (continued)
Re: Testing/Working on PyUNO? · Kevin Hunter Kesling
Re: Testing/Working on PyUNO? · Markus Mohrhard
Re: Testing/Working on PyUNO? · Kohei Yoshida
Re: Testing/Working on PyUNO? · James Michael DuPont
Re: Testing/Working on PyUNO? · Stephan Bergmann
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.