Re: [Libreoffice] 8 combinations of Python support: do we really need that?

Caolán McNamara <caolanm -AT- redhat.com>
Tue, 31 May 2011 10:34:30 +0100

On Tue, 2011-05-31 at 09:54 +0100, Michael Meeks wrote:

      IMHO - that is the thing that most needs fixing; I'd love to slave that
option to enable-python (personally). Then again - the other
--enable-ext-scripting-foo things also need IMHO to be auto-enabled if
the pre-requisites are there too so ... ;-)


We should default on the python-scripting extension alright, but outside
of the testing extension for them is there *really* a point to the rhino
and beanshell scripting engines ?

C.

Context

[Libreoffice] 8 combinations of Python support: do we really need that? · Tor Lillqvist
- Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Hanno Meyer-Thurow
  - Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Christian Lohmaier
    - Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Hanno Meyer-Thurow
- Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Michael Meeks
  - Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Caolán McNamara
  - Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Tor Lillqvist
  - Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Tor Lillqvist
  - (message not available)
    - Re: [Libreoffice] 8 combinations of Python support: do we really need that? · Michael Meeks

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.