Thank to you too! As a final comment, to those who might find this thread interesting, it may be worth pointing to PEP 394 (https://peps.python.org...

Thanks for the report (and the discussion!). I can see where you're coming from.. however, the basis for the gripe appears to be self-inflicted. It...

Note that according to chatgpt (I do not know how reliable it is on this, but it was quick), some distros (RedHat, Debian) make an explicit effort ...

In any case, I am happy with my LibO workaround. I would just like to share knowledge of this issue and of the workaround, since it would have save...

The #!/usr/bin/env is mostly a trick (some say a tiny abuse of env that was originally intended to change the environment) used to make scripts mo...

No, most use /usr/bin/env python...

No, it is specifically a LibO issue....

To work around the issue, it is enough to create a .local/bin/libreoffice executable file with:...

Also note that this isn't a LO issue, it would affect nearly every python program in the repos.

Obviously, another way to fix the issue is to build libreoffice like upstream does, with its own embedded python runtime, but it seems a bit of a w...

Why not, if Libreoffice can only work with the python it has been built against and no other?...

No, YOU made the choice to override the system python, the script should not disregard that choice

Not that normal. I would expect libreoffice to know which python it has been built against and use that one regardless of the virtual environment. ...

So you're overriding the system python then surprised when things break? Sounds pretty normal to me.