To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=97629
------- Additional comments from r...@openoffice.org Sun Mar 29 22:25:49 +0000 2009 ------- > This of course only fixes the problem when the OOo-specific python executable > (from the brand layer program directory) is used, not when a system-provided > python executable is used instead (i.e., OOo is configured to not provide an > own > python executable). Bad. Will this one day also be fixed for system-python builds? (It makes no sense for distros to ship an ancient, security buggy python internally which disallows even the usage of "standard" external modules instead of just using the python it has already - and all the modules with it..) --------------------------------------------------------------------- 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...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
