On Thu, 20 Oct 2011, Stephan Bergmann wrote:
(c) pyuno as run from an external python process might no longer work. An
easy way to test that is to start the interactive python executable from the
LibO program directory and execute "include uno" (and/or "include pyuno"; not
sure right now which one is the more interesting, but if both work I'd guess
that's good).
The solution we implemented for this for unoconv (a python tool) is to try
to load the pyuno.so with the system's python, on failure it looks for an
existing LibO python and swaps itself in memory with the LibO python and
tries again. That works quite well in practice.
--
-- dag wieers, dag@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, info@dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
Context
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.