|
|
 |
|
Title: Threads, Tkinter and asynchronous I/O
Submitter: Jacob Hallén
(other recipes)
Last Updated: 2001/10/21
Version no: 1.0
Category:
Threads
|
|
3 vote(s)
|
|
|
|
Description:
This recipe shows the easiest way of handling access to sockets, serial ports
and other asynchronous I/O ports while running a Tkinter based GUI.
It allows for a worker thread to block in a select(). Whenever something arrives
it will received and inserted in a queue. The main (GUI) thread then polls
the queue 10 times per second (often enough so the user will not notice any
significant delay), and processes all messages that have arrived.
Source: Text Source
"""
This recipe describes how to handle asynchronous I/O in an environment where
you are running Tkinter as the graphical user interface. Tkinter is safe
to use as long as all the graphics commands are handled in a single thread.
Since it is more efficient to make I/O channels to block and wait for something
to happen rather than poll at regular intervals, we want I/O to be handled
in separate threads. These can communicate in a threasafe way with the main,
GUI-oriented process through one or several queues. In this solution the GUI
still has to make a poll at a reasonable interval, to check if there is
something in the queue that needs processing. Other solutions are possible,
but they add a lot of complexity to the application.
Created by Jacob Hallén, AB Strakt, Sweden. 2001-10-17
"""
import Tkinter
import time
import threading
import random
import Queue
class GuiPart:
def __init__(self, master, queue, endCommand):
self.queue = queue
console = Tkinter.Button(master, text='Done', command=endCommand)
console.pack()
def processIncoming(self):
"""
Handle all the messages currently in the queue (if any).
"""
while self.queue.qsize():
try:
msg = self.queue.get(0)
print msg
except Queue.Empty:
pass
class ThreadedClient:
"""
Launch the main part of the GUI and the worker thread. periodicCall and
endApplication could reside in the GUI part, but putting them here
means that you have all the thread controls in a single place.
"""
def __init__(self, master):
"""
Start the GUI and the asynchronous threads. We are in the main
(original) thread of the application, which will later be used by
the GUI. We spawn a new thread for the worker.
"""
self.master = master
self.queue = Queue.Queue()
self.gui = GuiPart(master, self.queue, self.endApplication)
self.running = 1
self.thread1 = threading.Thread(target=self.workerThread1)
self.thread1.start()
self.periodicCall()
def periodicCall(self):
"""
Check every 100 ms if there is something new in the queue.
"""
self.gui.processIncoming()
if not self.running:
import sys
sys.exit(1)
self.master.after(100, self.periodicCall)
def workerThread1(self):
"""
This is where we handle the asynchronous I/O. For example, it may be
a 'select()'.
One important thing to remember is that the thread has to yield
control.
"""
while self.running:
time.sleep(rand.random() * 0.3)
msg = rand.random()
self.queue.put(msg)
def endApplication(self):
self.running = 0
rand = random.Random()
root = Tkinter.Tk()
client = ThreadedClient(root)
root.mainloop()
Discussion:
This seems to be a common problem, since there is a question about how to do it
a few times a month in comp.lang.pyhton. There are other solutions, involving
synchronisation between threads that will allow you to handle the problem
without the polling (the root.after()), but this is rather un-neat, since you
tend to get raising and waiting for semaphores all over your code.
In any case, a GUI already has a bunch of polling mechanisms built into it
(the main event loop), so adding one won't make much difference - especially
since it runs fairly seldom.
The code has only been tested under Linux, but it should work on any platform
with working threads.
|
|
Add comment
|
|
Number of comments: 3
FYI: This isn't Tkinter specific., Laura Creighton, 2001/12/04
If you want to replace the Tkinter code with wxPython code, that will work as well.
Laura Creighton lac@strakt.com
Add comment
Here's the same, but for PyQt, Boudewijn Rempt, 2002/04/15
"""
This recipe describes how to handle asynchronous I/O in an environment
where you are running PyQt as the graphical user interface. PyQt is
safe to use as long as all the graphics commands are handled in a
single thread. Since it is more efficient to make I/O channels to
block and wait for something to happen rather than poll at regular
intervals, we want I/O to be handled in separate threads. These can
communicate in a threasafe way with the main, GUI-oriented process
through one or several queues. In this solution the GUI still has to
make a poll at a reasonable interval, to check if there is something
in the queue that needs processing. Other solutions are possible, but
they add a lot of complexity to the application.
Created by Jacob Hallén, AB Strakt, Sweden. 2001-10-17
Adapted by Boudewijn Rempt, Netherlands. 2002-04-15
"""
import sys, time, threading, random, Queue, qt
class GuiPart(qt.QMainWindow):
def __init__(self, queue, endcommand, *args):
qt.QMainWindow.__init__(self, *args)
self.queue = queue
# We show the result of the thread in the gui, instead of the console
self.editor = qt.QMultiLineEdit(self)
self.setCentralWidget(self.editor)
self.endcommand = endcommand
def closeEvent(self, ev):
"""
We just call the endcommand when the window is closed
instead of presenting a button for that purpose.
"""
self.endcommand()
def processIncoming(self):
"""
Handle all the messages currently in the queue (if any).
"""
while self.queue.qsize():
try:
msg = self.queue.get(0)
# Check contents of message and do what it says
# As a test, we simply print it
self.editor.insertLine(str(msg))
except Queue.Empty:
pass
class ThreadedClient:
"""
Launch the main part of the GUI and the worker thread. periodicCall and
endApplication could reside in the GUI part, but putting them here
means that you have all the thread controls in a single place.
"""
def __init__(self):
# Create the queue
self.queue = Queue.Queue()
# Set up the GUI part
self.gui=GuiPart(self.queue, self.endApplication)
self.gui.show()
# A timer to periodically call periodicCall :-)
self.timer = qt.QTimer()
qt.QObject.connect(self.timer,
qt.SIGNAL("timeout()"),
self.periodicCall)
# Start the timer -- this replaces the initial call to periodicCall
self.timer.start(100)
# Set up the thread to do asynchronous I/O
# More can be made if necessary
self.running = 1
self.thread1 = threading.Thread(target=self.workerThread1)
self.thread1.start()
def periodicCall(self):
"""
Check every 100 ms if there is something new in the queue.
"""
self.gui.processIncoming()
if not self.running:
root.quit()
def endApplication(self):
self.running = 0
def workerThread1(self):
"""
This is where we handle the asynchronous I/O. For example, it may be
a 'select()'.
One important thing to remember is that the thread has to yield
control.
"""
while self.running:
# To simulate asynchronous I/O, we create a random number at
# random intervals. Replace the following 2 lines with the real
# thing.
time.sleep(rand.random() * 0.3)
msg = rand.random()
self.queue.put(msg)
rand = random.Random()
root = qt.QApplication(sys.argv)
client = ThreadedClient()
root.exec_loop()
It's amazing how similar these are. Two improvements: it doesn't use sys.exit, but asks the QApplication instance to quit, and it shows the result of the thread in the gui.
Add comment
Set thread subprocess as daemon, Alexander Belchenko, 2005/07/28
There is must be set thread as daemon by self.thread1.setDaemon(1) method:
self.running = 1
self.thread1 = threading.Thread(target=self.workerThread1)
self.thread1.setDaemon(1)
self.thread1.start()
Add comment
|
|
|
|
|
 |
|