Bug 167645 - MacOS: Can't run embedded Python externally since 25.2.4.2+. What are the alternatives?
Summary: MacOS: Can't run embedded Python externally since 25.2.4.2+. What are the alt...
Status: RESOLVED DUPLICATE of bug 167752
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.2.4.3 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-07-23 10:11 UTC by david
Modified: 2025-08-29 17:12 UTC (History)
0 users

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 david 2025-07-23 10:11:36 UTC
Description:
Apparently, this commit blocked the execution of embedded Python from outside LibreOffice:  
https://gerrit.libreoffice.org/c/core/+/185792

I understand that it improves security.

But now, how can we use the UNO API (document conversion, ...) on MacOS with a standard LibreOffice installation? Has this usage been permanently prohibited since that commit?

Using the system Python seems fragile (e.g. version mismatches when importing `pyuno.so` from LibreOffice, etc.).

I'm very interested in any hints or suggestions to help solve this.

Other related commit:
https://gerrit.libreoffice.org/c/core/+/187412

Thank you for your help!


Steps to Reproduce:
1. Install LibreOffice 25.2.4.2+
2. Run embedded python `/Applications/LibreOffice.app/Contents/Resources/python --version` 


Actual Results:
The Python process is being killed by the system (Code Signature Invalid).

Expected Results:
Python 3.x.x


Reproducible: Always


User Profile Reset: No

Additional Info:
.
Comment 1 Alex Thurgood 2025-08-29 17:12:38 UTC
As I'd confirmed this on bug 167752 (sorry, was just the first one I came across), marking this as DUP, and including the offending commit identification in that bug. Hopefully, someone will come up with an idea to on how to fix it that doesn't take 5 years to resolve.
Comment 2 Alex Thurgood 2025-08-29 17:12:49 UTC

*** This bug has been marked as a duplicate of bug 167752 ***