Python has a variety of GUIs available ... one of which, GTK, has been getting much more popular of late. As is common with many of the GUIs in Pyton and other languages, you'll typically write an application as follows:
- Initial code, defining
- Layout (Geometry)
- A main loop, which collects actions and events
Within the GUI, each widget must be defined, packed into the appropriate piece of Geometry, and shown (and the box and window containers also need to be shown) and - there you are - a simple GUI.
As you use the GUI, you'll want to provide your user with feedback by altering the text on labels, buttons, and making other widget changes. Slightly surprisingly, you define all the possible actions early on then have your events
trigger them as callback functions
The authors of GUI documentation always seem to start with a very very simple "hello world" example, then leap off into some quite extravagant further example, when all you (the programmer) want is a few buttons to perform tasks (and change to show what you've done).
Of course, I do know why they make them complicated as they've got dozens of events, scores of widgets and hundreds of facilities they would love you to use.
But I'm going to break from convention today and point you in the direction of a simple Python Gtk example that starts like this:
showing the basic elements of a window, a box, and a couple of widgets. Events are defined on the first two buttons that change the text and the quit button is (!!) programmed to quit the GUI.
As you run the GUI, you'll see the display counting up the number of times each button is pressed:
- thus completing that vital feedback element that you'll need in every GUI but never seems to be described in the manual until a footnote in chapter 5 or 6.
Complete (commented!) source code is here
where you'll find further examples as well. (written 2007-04-09, updated 2011-10-13)
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articlesY209 - Python GTK.Y212 - Python - Code testing, patterns, profiles and optimisation. 
Profiling your Python program - (2016-11-01) 
Pytest - second example beyond hello world - (2016-01-08) 
Pytest - starting example - (2016-01-07) 
The principle of mocking - and the Python Mock package - (2015-10-17) 
Unittest of a Flask application including forms - (2015-10-15) 
Flask and unittest - hello web app test world - (2015-10-15) 
Testing in Python 3 - unittest, doctest and __name__ == __main__ too. - (2015-04-21) 
Combining tests into suites, and suites into bigger suites - Python and unittest - (2015-03-01) 
Python base and inherited classes, test harness and unit testing - new examples - (2014-12-07) 
Learning to program - comments, documentation and test code - (2014-11-22) 
Test Driven Development in Python - Customer Comes First - (2013-05-16) 
Using Make for a distribution - (2012-03-17) 
Testing your Python classes with the unittest package - how to - (2011-10-14) 
Passing optional and named parameters to python methods - (2011-10-04) 
A demonstration of how many Python facilities work together - (2011-09-16) 
Pressing ^C in a Python program. Also Progress Bar. - (2011-09-15) 
Defining a static method - Java, Python and Ruby - (2010-02-01) 
Using Python with OpenOffice - (2009-04-09) 
Advanced Python, Perl, PHP and Tcl training courses / classes - (2008-02-25) 
Python decorators - wrapping a method call in extra code - (2007-04-15) 
__new__ v __init__ - python constructor alternatives? - (2007-04-14) 
Preparation for a day's work - (2005-03-04)
Some other Articles
Python dictionary for quick look upsA course in HelsinkiPlanters in the SpringA strong team broadens the professional coveragePython GTK - Widget, Packing, Event and Feedback exampleOvercrowded trains around BristolThe Holiday - unlikely romantic comedy?Wiltshire CirclesBuffering output - why it is done and issues raised in Tcl, Perl, Python and PHPGovernment pressure on me to shut up after I make the papers