Bug 47318 - Problem Installing Sparkline Extension related to Python
Summary: Problem Installing Sparkline Extension related to Python
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
Version:
(earliest affected)
3.5.1 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-14 13:13 UTC by Stephen Leibowitz
Modified: 2012-12-11 19:36 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Leibowitz 2012-03-14 13:13:43 UTC
I am getting an error while trying to install a free extension called EuroOffice Sparkline. The extension is listed in the OpenOffice extension catalog and also here:
http://www.multiracio.com/index.php?lang=en&style=eurooffice&page=eo_ext_sparkline

I have tried installing it in various ways. It succeeds in LibO Portable 3.4.5. But it fails in LibO Portable 3.5.0, LibO 3.5.1 RC2(not portable version), and OpenOffice Portable 3.2. I am including the three error messages at the end of this submission.

I contacted the extension author. Here is what he wrote:
********************
OpenOffice.org Portable is an alternative of OpenOffice.org. We have 
tested compatibility of our latest extensions on OpenOffice.org 3.2 and 
3.3, LibreOffice 3.3 and 3.4 and EuroOffice 2010. Please use one of 
these applications for avoiding any problems.
 
Tibor Brenner
********************

The website for the extension says, “Our extensions need Python 2.6 or newer versions.” I understand that the LibO 3.4 and 3.5 releases both use Python 2.6.1. However, the file location is slightly different:

3.4.5 (succeeds)
E:\PortableApps\LibreOfficePortable345\App\libreoffice\program\python.exe

3.5.0 (fails)
E:\PortableApps\LibreOfficePortable\App\libreoffice\program\python-core-2.6.1\bin\python.exe

My system is a Win XP SP3 with 4GB RAM.

Here are the three error messages:

********************

(LibreOffice Portable 3.5.0)
Extension Manager

(com.sun.star.uno.RuntimeException)
{ { Message = "<type
‘exceptions.AttributeError'>: ‘module’ object has
no attribute 'writeRegistryInfo', traceback
fol|ows\X000a
E:\\PortableApps\\LibreOfficePortable\\App\\libre
office\\program\\pythonloader.py:158 in function
writeRegistryInfo() [return
mod .writeRegistryInfo( self.ctx.ServiceManager,
regKey )]\X000a\X000a", Context =
(com .sun.star.uno.XInterface) @0 } }

********************

(LibreOffice 3.5.1 RC2 [not portable version])
Extension Manager

(com.sun.star.uno.RuntimeException)
{ { Message = "<type
‘exceptions.AttributeError'>: ‘module’ object has
no attribute 'writeRegistryInfo', traceback
follows\X000a C:\\Program Files\\LibreOffice
3.5\\program\\pythonloader.py:158 in function
writeRegistryInfo() [return
mod.writeRegistryInfo( self.ctx.ServiceManager,
regKey )]\X000a\X000a", Context =
(com.sun.star.uno.XInterface) @0 } }

********************

(OpenOffice Portable 3.2)
Extension Manager

(com.sun.star.uno.RuntimeException)
{ { Message = "<type
‘exceptions.AttributeError'>: 'module' object has
no attribute 'writeRegistryInfo', traceback
follows\X000a
E:\\PortableApps\\OpenOfficePortable\\App\\open
office\\Basis\\program\\pythonloader.py:142 in
function writeRegistryInfo() [return
mod .writeRegistryInfo( self.ctx.ServiceManager,
regKey )]\X000a", Context =
(com .sun.star.uno.XInterface) @0 } }

********************
Comment 1 hanya 2012-04-03 01:08:38 UTC
This is caused by the changes of 3.5.x. 
I got the following message with debug mode: 

TypeError: Error when calling the metaclass bases
    Cannot create a consistent method resolution
order (MRO) for bases object, Base, com.sun.star.beans.XPropertySet, com.sun.star.lang.XServiceInfo

This is caused by the multiple inheritance of unohelper.Base class of the class. 
But the extension package contains only pyc files, so we can do nothing on it.
Comment 2 Joel Madero 2012-12-11 19:36:07 UTC
IMO this is an issue that the creator of the extension should look at (if he/she wants it to be compatible with LibO). Furthermore, extensions taken from AOO site aren't guaranteed to work with LibO at all as our code is different.

I'm marking this as INVALID as it's a bug against an extension that is intended for AOO not LibO. My recommendation is to send the developer a message requesting that they make it available for LibO.

Thanks for your understanding and patience with getting someone to look at this one.