https://bugs.documentfoundation.org/show_bug.cgi?id=167752
Christian Lohmaier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |g --- Comment #5 from Christian Lohmaier <[email protected]> --- marking this as duplicate of 167645 - it is an intentional change, since otherwise LibreOffice's permissions that the user grants to LibreOffice could be abused by random other processes, in effect bypassing macOS security. I honestly don't really have a good idea on how to solve this dilemma - for now using your own python runtime (or initiating the calls via LibreOffice) are the only options. Of course open for ideas on how this can be solved technically without nullifying that measure... https://developer.apple.com/documentation/security/applying-launch-environment-and-library-constraints is starting point for Apple's docs. I guess it could help to have concrete use case description as for what the python runtime shipped with LibreOffice should be used for when called externally. Document conversion can be done by launching a macro/entry point via LibreOffice. https://wiki.documentfoundation.org/Documentation/DevGuide/Scripting_Framework#Python_script e.g. 'vnd.sun.star.script:TableSample.py$createTable?langauge=Python&location=share' for the one of the samples that create a new writer document and inserts some text and a table. So the workaround would be to create an extension that does what you want and deploy that, then you can call the script from the extension (or place the files manually) -- You are receiving this mail because: You are the assignee for the bug.
