Tk

jklymak · jklymak · commit 5f4a18cad282 · 2023-09-01T08:18:09.000-07:00
diff --git a/galleries/users_explain/figure/backends.rst b/galleries/users_explain/figure/backends.rst
@@ -12,17 +12,16 @@ What is a backend?
 ------------------
 
 Backends are used for out-putting Matplotlib figures (see :ref:`figure-intro`),
-to the screen or for writing to files.  A lot of
-documentation on the website and in the mailing lists refers to the "backend"
-and many new users are confused by this term. Matplotlib targets many different
-use cases and output formats.  Some people use Matplotlib interactively from
-the Python shell and have plotting windows pop up when they type commands.
-Some people run `Jupyter <https://jupyter.org>`_ notebooks and draw inline
-plots for quick data analysis. Others embed Matplotlib into graphical user
-interfaces like PyQt or PyGObject to build rich applications.  Some people use
-Matplotlib in batch scripts to generate postscript images from numerical
-simulations, and still others run web application servers to dynamically serve
-up graphs.
+to the screen or for writing to files.  A lot of documentation on the website
+and in the mailing lists refers to the "backend" and many new users are
+confused by this term. Matplotlib targets many different use cases and output
+formats.  Some people use Matplotlib interactively from the Python shell and
+have plotting windows pop up when they type commands. Some people run `Jupyter
+<https://jupyter.org>`_ notebooks and draw inline plots for quick data
+analysis. Others embed Matplotlib into graphical user interfaces like PyQt or
+PyGObject to build rich applications.  Some people use Matplotlib in batch
+scripts to generate postscript images from numerical simulations, and still
+others run web application servers to dynamically serve up graphs.
 
 To support all of these use cases, Matplotlib can target different
 outputs, and each of these capabilities is called a backend; the
@@ -286,8 +285,8 @@ point is to ensure that your GUI toolkit is installed properly, taking
 Matplotlib our of the testing.  Almost all GUI toolkits have a small test
 program that can be run to test basic functionality.  If this test fails, try re-installing.
 
-PyQT
-^^^^
+PyQt(5,6) and PySide
+^^^^^^^^^^^^^^^^^^^^
 
 .. code-block:: bash
 
@@ -296,12 +295,19 @@ PyQT
 If you have ``PySide`` or ``PyQT6`` installed instead, just change the import
 accordingly
 
+tkinter
+^^^^^^^
+
+.. code-block:: bash
+
+   python3 -c "from tkinter import Tk; Tk().mainloop()"
+
 GTK
 ^^^
 
 .. code-block:: bash
 
-   python3 -c 'from gi.repository import Gtk; win = Gtk.Window(); win.connect("destroy", Gtk.main_quit); win.show(); Gtk.main()'
+   python3 -c "from gi.repository import Gtk; win = Gtk.Window(); win.connect('destroy', Gtk.main_quit); win.show(); Gtk.main()""
 
 wxPython
 ^^^^^^^^
