[Solved, Issues] LibreOffice has been released today

[Villeroy]

http://blog.documentfoundation.org/2011 ... ffice-3-3/

[hanya]

Python implementation of LO 3.3.0 is completely broken on Windows environment. Any extension and any scripts can not be used on LO 3.3 working in Windows OS. It will be fixed on 3.3.1.
https://bugs.freedesktop.org/show_bug.cgi?id=33355

[Villeroy]

Python implementation of LO 3.3.0 is completely broken on Windows environment. Any extension and any scripts can not be used on LO 3.3 working in Windows OS. It will be fixed on 3.3.1.
https://bugs.freedesktop.org/show_bug.cgi?id=33355

So I can not install it on our Windows boxes. Thank you for the info.

Another problem on my Ubuntu 10.4 box:
File>New>Database...
Connect to existing db
crashes instantly when I pick the LDAP entry from the list box.

https://bugs.freedesktop.org/show_bug.cgi?id=32561

[crusader]

Python implementation of LO 3.3.0 is completely broken on Windows environment. Any extension and any scripts can not be used on LO 3.3 working in Windows OS. It will be fixed on 3.3.1.

For those of us who only know python as the giant snake in the Amazon, what does all this mean -- in plain English? Is it not worth downloading and using LO 3.3 for those of us still enslaved by Windows?

[FJCC]

Python is a programming language:http://www.python.org/. It is included with OpenOffice.org and LibreOffice and, I suppose, all other OOo related products. It can be used to write macros and extensions. It is not used in the basic functioning of the office suite. I don't know which extensions are written in Python, but if you don't use many extensions, this will not affect you.

[franx]

Hi,

please see also the workaround (comment #7), described in
→ Bug 33355 - Python scripting not available
<https://bugs.freedesktop.org/show_bug.cgi?id=33355>

From my comment (#8):
"With <pythonloader.uno.dll> from OOo 3.3 RC10--copied to LibO 3.3 RC4--
my issues were fixed (s. comment #3), and the Python scripts list is perfect."

In short:
Rename pythonloader.uno.dll in <LibO_installation>\Basis\program
to pythonloader.uno.dll.bak.
Replace it with pythonloader.uno.dll from OOo 3.3.

Download
→ pythonloader.uno.dll [from OOo 3.3]
<http://dl.dropbox.com/u/19264180/pythonloader.uno.dll>
21 KB
md5sum: 16a1fb546d2bda157d207e9b0bedaa9e

[kenirving]

This is pretty clear, but I couldn't get it to work on Windows Vista.

[franx]

Hi kenirving,

that's pretty short.

What does not work?
- You cannot rename pythonloader.uno.dll?
- You cannot add the new file pythonloader.uno.dll?
- HelloWorldPython doesn't appear in the list?
- Run doesn't work?

[DACM]

LibreOffice Portable 3.3.0 was also officially released today for the Windows platform. So if you're a Windows user, you can run the LibreOffice suite from a USB key, attached storage, network drive, or from the Cloud with all your settings intact, without installing anything on the host (Windows) computer.

Also note the associated JPortable (Java Portable) update.

I haven't tested the Python bug with this release but I would imagine you'll need the workaround if you use Python extensions or Python-coded macros.

And I'm looking forward to testing for persistent 'Class Path' settings, as these were not persistent in previous 'Portable' versions and we were promised a fix by John Haller of PortableApps.com.

Edit: As promised, the 'Class Path' settings are now persistent in 'Portable' versions as of 3.3.0.

[vasa1]

LibreOffice Portable 3.3.0 was also officially released today for the Windows platform. So if you're a Windows user, you can run the LibreOffice suite from a USB key, attached storage, network drive, or from the Cloud with all your settings intact, without installing anything on the host (Windows) computer...

For reasons explained on the portableapps.com site, the download of the portableapps version is about 100 MB smaller than the non-portable.

[Cambirder]

For those of us who only know python as the giant snake in the Amazon

Those giant snakes are Anacondas which as far as I know are not part of OOo