[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 User ace_dent changed the following: What|Old value |New value Status|RESOLVED |VERIFIED Keywords| |oooqa Status|VERIFIED |CLOSED --- Additional comments from ace_d...@openoffice.org Sat May 17 20:52:26 + 2008 --- The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html --- Additional comments from ace_d...@openoffice.org Sat May 17 22:56:47 + 2008 --- As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew --- Additional comments from bill_jans...@openoffice.org Wed Jan 21 01:57:59 + 2009 --- I'm afraid this issue should never have been closed. Python UNO is still broken in 3.0.1rc2 on Intel Macs running OS X 10.5.x (and PPC Macs running OS X 10.5.x). The "system Python" on OS X 10.5 is a different version (2.5) than on 10.4 (which uses 2.3). I believe that debyld was correct in pointing out that the Python to be used should be the system Python. This implies that you need two different pyuno.so libraries for 10.4 and 10.5 -- you cannot use the same one on the two different platforms. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@porting.openoffice.org For additional commands, e-mail: issues-h...@porting.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 --- Additional comments from [EMAIL PROTECTED] Mon Jan 8 15:03:37 -0800 2007 --- pjanik, In response to you last comment as I don't think my point has been understood. > if you use specific python, you can also compile specific uno extension. Sure this can be done in isolated situation but you don't want to have general users compiling uno just because they use a different python. What happens with Mac update their python/ > Hmm, we can't support all versions. Distributing python doesn't make sense, because: You don't have to support all versions just the one required for OOo. > - people do already have it on their systems Users will have the wrong one if they upgrade, and what if Mac release the OS with the new version? You will have to always distribute a copy of OOo every time the OS changes to match the version of python. > - not all people want to use it You are only distributing the "python-core" with OOo not installing it on their system just as with Windows and Linux OS's. > So the default is to use system python. > Special cases need special treatment I am not sure what you mean by this but either way by my understanding if you rely on the native python then not only those who wish to automate OOo are affected but those who use python macros will dependent on the version of python installed. Distributing OOo with python means you are not dependent on the native version installed and don't have to updated all the builds when the MAC OS python is updated. Can this be put down for discussion somewhere and see what others think? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 User pjanik changed the following: What|Old value |New value Status|NEW |RESOLVED Resolution| |INVALID --- Additional comments from [EMAIL PROTECTED] Sun Jan 7 23:53:22 -0800 2007 --- debyld: if you use specific python, you can also compile specific uno extension. Hmm, we can't support all versions. Distributing python doesn't make sense, because: - people do already have it on their systems - not all people want to use it So the default is to use system python. Special cases need special treatment. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 --- Additional comments from [EMAIL PROTECTED] Sun Jan 7 23:48:06 -0800 2007 --- In summary do you agree this issue should be closed as invalid because: (a) it works with the default system python which is 2.3.5 (b) DYLD_LIBRARY_PATH is also set before launching soffice.bin (I think?- please have a look inside the shell script named "soffice" (c) the internal build would still tie everyone to some specific version (it would most likely be 2.3.5 for now, see issue 59850) You could make different issues to suggest using a later version or to allow any version, but i have no idea what would be meaningful... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 --- Additional comments from [EMAIL PROTECTED] Sun Jan 7 22:31:58 -0800 2007 --- sparcmoz, Thanks for that however, it only works if you are using python2.3 which is not very future safe (see below for the result) as I am using python 2.4.3 by default and, it relies on the DYLD_LIBRARY_PATH being set, which is not by default. It would be best and easiest I would expect to go back to the way it was and include the required python with OOo as with versions 2.0-. What do you think? /Applications/OpenOffice.org 2.1.app/Contents/MacOS/program debyld$ which python /opt/local/bin/python /Applications/OpenOffice.org 2.1.app/Contents/MacOS/program debyld$ set | grep DYLD DYLD_LIBRARY_PATH=. /Applications/OpenOffice.org 2.1.app/Contents/MacOS/program debyld$ python Python 2.4.3 (#1, Aug 31 2006, 09:01:48) [GCC 4.0.0 (Apple Computer, Inc. build 5026)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import uno Fatal Python error: Interpreter not initialized (version mismatch?) Abort trap /Applications/OpenOffice.org 2.1.app/Contents/MacOS/program debyld$ python2.3 Python 2.3.5 (#1, Mar 20 2005, 20:38:20) [GCC 3.3 20030304 (Apple Computer, Inc. build 1809)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import uno >>> ^D - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 --- Additional comments from [EMAIL PROTECTED] Sun Jan 7 22:10:42 -0800 2007 --- The following is on a ppc this time: imac:/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program jim$ which python /usr/bin/python imac:/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program jim$ set | grep DYLD imac:/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program jim$ export DYLD_LIBRARY_PATH=. imac:/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program jim$ /usr/bin/python Python 2.3.5 (#1, Oct 5 2005, 11:07:27) [GCC 3.3 20030304 (Apple Computer, Inc. build 1809)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import uno >>> help Type help() for interactive help, or help(object) for help about object. >>> ^D imac:/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program jim$ Please post your output for the same steps so we can compare.. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 --- Additional comments from [EMAIL PROTECTED] Sun Jan 7 21:35:27 -0800 2007 --- sparcmoz, Setting the DYLD_LIBRARY_PATH didn't seem to work. Running python from within OOo program directory to load the uno lib I get: >>> import uno Fatal Python error: Interpreter not initialized (version mismatch?) Abort trap - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 User sparcmoz changed the following: What|Old value |New value Ever confirmed| |1 Status|UNCONFIRMED |NEW --- Additional comments from [EMAIL PROTECTED] Fri Jan 5 19:02:19 -0800 2007 --- @debyld: I can reproduce this on Mac Intel. I noticed by accident, that this problem is not seen when working in a building environment. After reviewing the environment I tried this in the program directory: $ export DYLD_LIBRARY_PATH=. ...and now there is no more error message. Do things then work as expected? I don't know if that would be an acceptable fix, but at least it might confirm the problem. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 User mh changed the following: What|Old value |New value Assigned to|mh|ericb Subcomponent|code |MacOSX --- Additional comments from [EMAIL PROTECTED] Thu Jan 4 03:02:13 -0800 2007 --- change subcomponent - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 User sparcmoz changed the following: What|Old value |New value CC|''|'sparcmoz' - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[porting-issues] [Issue 73101] unable to import uno modul e
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73101 User of changed the following: What|Old value |New value Assigned to|tm|mh Component|framework |porting QA contact|[EMAIL PROTECTED] |[EMAIL PROTECTED] --- Additional comments from [EMAIL PROTECTED] Thu Jan 4 02:32:22 -0800 2007 --- reassigned - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]