On 10/21/2011 01:20 AM, Miklos Vajna wrote:
On Thu, Oct 20, 2011 at 11:21:52PM +0200, Stephan Bergmannsberg...@redhat.com
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
On Thu, 2011-10-20 at 23:21 +0200, Stephan Bergmann wrote:
I must confess ...
Heh :-) seems reasonable enough.
Anyway, if anybody less Windows-phobic than me would like to check out
whether pyuno still works on Windows, that would be great:
In the past I've had similar
On Fri, 2011-10-21 at 09:25 +0100, Michael Meeks wrote:
What would be -really- excellent to nail this permanently would be to
have a during-compile unit test that exercises pyuno, clearly getting
that working on Linux first would be ideal.
Which reminds me - do we not have bridge-test
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
I must confess that in
http://cgit.freedesktop.org/libreoffice/core/commit/?id=fecde94354a46463d346a1a78962f39a5a6f9eb8
Undo basis/brand split: moved Python from basis to brand. I did some
blind changes to Windows-only code in pyuno/zipcore/python.cxx. (Did I
mention I still did not succeed
On Thu, Oct 20, 2011 at 11:21:52PM +0200, Stephan Bergmann
sberg...@redhat.com 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