https://bugs.documentfoundation.org/show_bug.cgi?id=157624
Bug ID: 157624
Summary: tkinter Missing From LibreOffice Python Interpreter
Product: LibreOffice
Version: 7.6.1.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: tomekl...@gmail.com
Description:
tkinter works beautifully under LibreOffice. It can be used in Linux without
any problem (Linux LibreOffice uses system Python interpreter if LibreOffice is
installed using packaging system like deb/rpm). But on Windows, Mac and
LibreOffice installed in Linux using e.g. flatpak, LibreOffice has its own
Python interpreter packaged. This interpreter is missing tkinter. Other Python
packages can be added using pip but not tkinter. If tkinter is not a part of a
Python interpreter, there is no way to add it later.
Steps to Reproduce:
1. there is no way to add tkinter to LibreOffice Python interpreter
Actual Results:
tkinter works nicely but can not be added
Expected Results:
tkinter should be the default part of the packaged Python interpreter
Reproducible: Always
User Profile Reset: No
Additional Info:
It is very sad that there are very limited possibilities regarding GUI
frameworks in Python in LibreOffice. Only UNO dialogs really work. Under Linux,
tkinter works without problems but it can not be used on Windows/Mac/Linux with
LO installed using flatpak.
Also PyQT and PySide actually work very nicely! But after closing a PyQT
window, LibreOffice always crashes (new versions of LO. In older versions of
LO, PyQT/PySide just worked).
Many other GUI frameworks do not work under LibreOffice (I tested Dear PyGUI,
Toga, PySimpleGUI, wxPython, Kivy, Pywebview). It is interesting that many of
them actually work but only after closing a window, the whole LibreOffice
freezes or crashes or the window can not be closed (destroy method does not
work).
So, there are really no options, just UNO dialog windows and forms which are
unknown to almost all Pythonists.
--
You are receiving this mail because:
You are the assignee for the bug.
