https://bugs.documentfoundation.org/show_bug.cgi?id=116412
--- Comment #10 from Jan-Marek Glogowski <[email protected]> --- Python UNO is a shared library, which uses CPython memory functions, which have different signatures between CPython versions. LO just ships a single Python UNO shared lib for our own Python. Linux distros build LO against the system Python, so don't have this restricted modules problem. I don't have any opinion on the disabled modules. Probably someone wanted to keep a low(er) security profile? Maybe additional dependencies would be needed? And the LO UI unit tests use Python and it's needed for the build, but can be disabled for scripting. Implementation options: 1. Ship additional Python UNO shared libraries so external Python can be used It's probably a lot of work to implement in gbuild; IMHO "impossible" 2. Switch UNO CPython symbol lookup from compile to runtime (dlsym, etc.) This should generally be possible, is much easier and in theory should be a longer weekend project, if these needed functions aren't inline'd. Then a user could simply install any CPython and use it for scripting, avoiding the problem alltogether. And you need to find somebody, who actually cares about this ;-) -- You are receiving this mail because: You are the assignee for the bug.
