Antoine Pitrou | 64a467d | 2010-12-12 20:34:49 +0000 | [diff] [blame] | 1 | :mod:`threading` --- Thread-based parallelism |
| 2 | ============================================= |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 3 | |
| 4 | .. module:: threading |
Antoine Pitrou | 64a467d | 2010-12-12 20:34:49 +0000 | [diff] [blame] | 5 | :synopsis: Thread-based parallelism. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 6 | |
Raymond Hettinger | 1048094 | 2011-01-10 03:26:08 +0000 | [diff] [blame] | 7 | **Source code:** :source:`Lib/threading.py` |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 8 | |
Raymond Hettinger | 4f707fd | 2011-01-10 19:54:11 +0000 | [diff] [blame] | 9 | -------------- |
| 10 | |
Georg Brandl | 2067bfd | 2008-05-25 13:05:15 +0000 | [diff] [blame] | 11 | This module constructs higher-level threading interfaces on top of the lower |
| 12 | level :mod:`_thread` module. See also the :mod:`queue` module. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 13 | |
| 14 | The :mod:`dummy_threading` module is provided for situations where |
Georg Brandl | 2067bfd | 2008-05-25 13:05:15 +0000 | [diff] [blame] | 15 | :mod:`threading` cannot be used because :mod:`_thread` is missing. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 16 | |
Benjamin Peterson | 8bdd545 | 2008-08-18 22:38:41 +0000 | [diff] [blame] | 17 | .. note:: |
| 18 | |
Benjamin Peterson | b3085c9 | 2008-09-01 23:09:31 +0000 | [diff] [blame] | 19 | While they are not listed below, the ``camelCase`` names used for some |
| 20 | methods and functions in this module in the Python 2.x series are still |
| 21 | supported by this module. |
Benjamin Peterson | 8bdd545 | 2008-08-18 22:38:41 +0000 | [diff] [blame] | 22 | |
Antoine Pitrou | 0034281 | 2011-01-06 16:31:28 +0000 | [diff] [blame] | 23 | .. impl-detail:: |
| 24 | |
Ezio Melotti | ff12fae | 2013-01-18 19:55:46 +0200 | [diff] [blame] | 25 | In CPython, due to the :term:`Global Interpreter Lock`, only one thread |
Antoine Pitrou | 0034281 | 2011-01-06 16:31:28 +0000 | [diff] [blame] | 26 | can execute Python code at once (even though certain performance-oriented |
| 27 | libraries might overcome this limitation). |
Ezio Melotti | ff12fae | 2013-01-18 19:55:46 +0200 | [diff] [blame] | 28 | If you want your application to make better use of the computational |
Antoine Pitrou | 0034281 | 2011-01-06 16:31:28 +0000 | [diff] [blame] | 29 | resources of multi-core machines, you are advised to use |
| 30 | :mod:`multiprocessing` or :class:`concurrent.futures.ProcessPoolExecutor`. |
| 31 | However, threading is still an appropriate model if you want to run |
| 32 | multiple I/O-bound tasks simultaneously. |
| 33 | |
Antoine Pitrou | 0034281 | 2011-01-06 16:31:28 +0000 | [diff] [blame] | 34 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 35 | This module defines the following functions and objects: |
| 36 | |
| 37 | |
Benjamin Peterson | 672b803 | 2008-06-11 19:14:14 +0000 | [diff] [blame] | 38 | .. function:: active_count() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 39 | |
| 40 | Return the number of :class:`Thread` objects currently alive. The returned |
Benjamin Peterson | 4ac9ce4 | 2009-10-04 14:49:41 +0000 | [diff] [blame] | 41 | count is equal to the length of the list returned by :func:`.enumerate`. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 42 | |
| 43 | |
| 44 | .. function:: Condition() |
| 45 | :noindex: |
| 46 | |
| 47 | A factory function that returns a new condition variable object. A condition |
| 48 | variable allows one or more threads to wait until they are notified by another |
| 49 | thread. |
| 50 | |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 51 | See :ref:`condition-objects`. |
| 52 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 53 | |
Benjamin Peterson | 672b803 | 2008-06-11 19:14:14 +0000 | [diff] [blame] | 54 | .. function:: current_thread() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 55 | |
| 56 | Return the current :class:`Thread` object, corresponding to the caller's thread |
| 57 | of control. If the caller's thread of control was not created through the |
| 58 | :mod:`threading` module, a dummy thread object with limited functionality is |
| 59 | returned. |
| 60 | |
| 61 | |
| 62 | .. function:: enumerate() |
| 63 | |
Benjamin Peterson | 672b803 | 2008-06-11 19:14:14 +0000 | [diff] [blame] | 64 | Return a list of all :class:`Thread` objects currently alive. The list |
| 65 | includes daemonic threads, dummy thread objects created by |
| 66 | :func:`current_thread`, and the main thread. It excludes terminated threads |
| 67 | and threads that have not yet been started. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 68 | |
| 69 | |
| 70 | .. function:: Event() |
| 71 | :noindex: |
| 72 | |
| 73 | A factory function that returns a new event object. An event manages a flag |
Georg Brandl | 502d9a5 | 2009-07-26 15:02:41 +0000 | [diff] [blame] | 74 | that can be set to true with the :meth:`~Event.set` method and reset to false |
| 75 | with the :meth:`clear` method. The :meth:`wait` method blocks until the flag |
| 76 | is true. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 77 | |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 78 | See :ref:`event-objects`. |
| 79 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 80 | |
| 81 | .. class:: local |
| 82 | |
| 83 | A class that represents thread-local data. Thread-local data are data whose |
| 84 | values are thread specific. To manage thread-local data, just create an |
| 85 | instance of :class:`local` (or a subclass) and store attributes on it:: |
| 86 | |
| 87 | mydata = threading.local() |
| 88 | mydata.x = 1 |
| 89 | |
| 90 | The instance's values will be different for separate threads. |
| 91 | |
| 92 | For more details and extensive examples, see the documentation string of the |
| 93 | :mod:`_threading_local` module. |
| 94 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 95 | |
| 96 | .. function:: Lock() |
| 97 | |
| 98 | A factory function that returns a new primitive lock object. Once a thread has |
| 99 | acquired it, subsequent attempts to acquire it block, until it is released; any |
| 100 | thread may release it. |
| 101 | |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 102 | See :ref:`lock-objects`. |
| 103 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 104 | |
| 105 | .. function:: RLock() |
| 106 | |
| 107 | A factory function that returns a new reentrant lock object. A reentrant lock |
| 108 | must be released by the thread that acquired it. Once a thread has acquired a |
| 109 | reentrant lock, the same thread may acquire it again without blocking; the |
| 110 | thread must release it once for each time it has acquired it. |
| 111 | |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 112 | See :ref:`rlock-objects`. |
| 113 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 114 | |
Georg Brandl | 7f01a13 | 2009-09-16 15:58:14 +0000 | [diff] [blame] | 115 | .. function:: Semaphore(value=1) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 116 | :noindex: |
| 117 | |
| 118 | A factory function that returns a new semaphore object. A semaphore manages a |
| 119 | counter representing the number of :meth:`release` calls minus the number of |
| 120 | :meth:`acquire` calls, plus an initial value. The :meth:`acquire` method blocks |
| 121 | if necessary until it can return without making the counter negative. If not |
| 122 | given, *value* defaults to 1. |
| 123 | |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 124 | See :ref:`semaphore-objects`. |
| 125 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 126 | |
Georg Brandl | 7f01a13 | 2009-09-16 15:58:14 +0000 | [diff] [blame] | 127 | .. function:: BoundedSemaphore(value=1) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 128 | |
| 129 | A factory function that returns a new bounded semaphore object. A bounded |
| 130 | semaphore checks to make sure its current value doesn't exceed its initial |
| 131 | value. If it does, :exc:`ValueError` is raised. In most situations semaphores |
| 132 | are used to guard resources with limited capacity. If the semaphore is released |
| 133 | too many times it's a sign of a bug. If not given, *value* defaults to 1. |
| 134 | |
| 135 | |
| 136 | .. class:: Thread |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 137 | :noindex: |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 138 | |
| 139 | A class that represents a thread of control. This class can be safely |
| 140 | subclassed in a limited fashion. |
| 141 | |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 142 | See :ref:`thread-objects`. |
| 143 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 144 | |
| 145 | .. class:: Timer |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 146 | :noindex: |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 147 | |
| 148 | A thread that executes a function after a specified interval has passed. |
| 149 | |
Georg Brandl | 179249f | 2010-08-26 14:30:15 +0000 | [diff] [blame] | 150 | See :ref:`timer-objects`. |
| 151 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 152 | |
| 153 | .. function:: settrace(func) |
| 154 | |
| 155 | .. index:: single: trace function |
| 156 | |
| 157 | Set a trace function for all threads started from the :mod:`threading` module. |
| 158 | The *func* will be passed to :func:`sys.settrace` for each thread, before its |
| 159 | :meth:`run` method is called. |
| 160 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 161 | |
| 162 | .. function:: setprofile(func) |
| 163 | |
| 164 | .. index:: single: profile function |
| 165 | |
| 166 | Set a profile function for all threads started from the :mod:`threading` module. |
| 167 | The *func* will be passed to :func:`sys.setprofile` for each thread, before its |
| 168 | :meth:`run` method is called. |
| 169 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 170 | |
| 171 | .. function:: stack_size([size]) |
| 172 | |
| 173 | Return the thread stack size used when creating new threads. The optional |
| 174 | *size* argument specifies the stack size to be used for subsequently created |
| 175 | threads, and must be 0 (use platform or configured default) or a positive |
| 176 | integer value of at least 32,768 (32kB). If changing the thread stack size is |
| 177 | unsupported, a :exc:`ThreadError` is raised. If the specified stack size is |
| 178 | invalid, a :exc:`ValueError` is raised and the stack size is unmodified. 32kB |
| 179 | is currently the minimum supported stack size value to guarantee sufficient |
| 180 | stack space for the interpreter itself. Note that some platforms may have |
| 181 | particular restrictions on values for the stack size, such as requiring a |
| 182 | minimum stack size > 32kB or requiring allocation in multiples of the system |
| 183 | memory page size - platform documentation should be referred to for more |
| 184 | information (4kB pages are common; using multiples of 4096 for the stack size is |
| 185 | the suggested approach in the absence of more specific information). |
| 186 | Availability: Windows, systems with POSIX threads. |
| 187 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 188 | |
Antoine Pitrou | 7c3e577 | 2010-04-14 15:44:10 +0000 | [diff] [blame] | 189 | This module also defines the following constant: |
| 190 | |
| 191 | .. data:: TIMEOUT_MAX |
| 192 | |
| 193 | The maximum value allowed for the *timeout* parameter of blocking functions |
| 194 | (:meth:`Lock.acquire`, :meth:`RLock.acquire`, :meth:`Condition.wait`, etc.). |
Georg Brandl | 6faee4e | 2010-09-21 14:48:28 +0000 | [diff] [blame] | 195 | Specifying a timeout greater than this value will raise an |
Antoine Pitrou | 7c3e577 | 2010-04-14 15:44:10 +0000 | [diff] [blame] | 196 | :exc:`OverflowError`. |
| 197 | |
Antoine Pitrou | adbc009 | 2010-04-19 14:05:51 +0000 | [diff] [blame] | 198 | .. versionadded:: 3.2 |
Antoine Pitrou | 7c3e577 | 2010-04-14 15:44:10 +0000 | [diff] [blame] | 199 | |
Georg Brandl | 67b21b7 | 2010-08-17 15:07:14 +0000 | [diff] [blame] | 200 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 201 | Detailed interfaces for the objects are documented below. |
| 202 | |
| 203 | The design of this module is loosely based on Java's threading model. However, |
| 204 | where Java makes locks and condition variables basic behavior of every object, |
| 205 | they are separate objects in Python. Python's :class:`Thread` class supports a |
| 206 | subset of the behavior of Java's Thread class; currently, there are no |
| 207 | priorities, no thread groups, and threads cannot be destroyed, stopped, |
| 208 | suspended, resumed, or interrupted. The static methods of Java's Thread class, |
| 209 | when implemented, are mapped to module-level functions. |
| 210 | |
| 211 | All of the methods described below are executed atomically. |
| 212 | |
| 213 | |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 214 | .. _thread-objects: |
| 215 | |
| 216 | Thread Objects |
| 217 | -------------- |
| 218 | |
| 219 | This class represents an activity that is run in a separate thread of control. |
| 220 | There are two ways to specify the activity: by passing a callable object to the |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 221 | constructor, or by overriding the :meth:`~Thread.run` method in a subclass. |
| 222 | No other methods (except for the constructor) should be overridden in a |
| 223 | subclass. In other words, *only* override the :meth:`~Thread.__init__` |
| 224 | and :meth:`~Thread.run` methods of this class. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 225 | |
| 226 | Once a thread object is created, its activity must be started by calling the |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 227 | thread's :meth:`~Thread.start` method. This invokes the :meth:`~Thread.run` |
| 228 | method in a separate thread of control. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 229 | |
| 230 | Once the thread's activity is started, the thread is considered 'alive'. It |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 231 | stops being alive when its :meth:`~Thread.run` method terminates -- either |
| 232 | normally, or by raising an unhandled exception. The :meth:`~Thread.is_alive` |
| 233 | method tests whether the thread is alive. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 234 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 235 | Other threads can call a thread's :meth:`~Thread.join` method. This blocks |
| 236 | the calling thread until the thread whose :meth:`~Thread.join` method is |
| 237 | called is terminated. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 238 | |
| 239 | A thread has a name. The name can be passed to the constructor, and read or |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 240 | changed through the :attr:`~Thread.name` attribute. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 241 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 242 | A thread can be flagged as a "daemon thread". The significance of this flag |
| 243 | is that the entire Python program exits when only daemon threads are left. |
| 244 | The initial value is inherited from the creating thread. The flag can be |
| 245 | set through the :attr:`~Thread.daemon` property. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 246 | |
Antoine Pitrou | 38b8254 | 2013-02-15 21:27:18 +0100 | [diff] [blame^] | 247 | .. note:: |
| 248 | Daemon threads are abruptly stopped at shutdown. Their resources (such |
| 249 | as open files, database transactions, etc.) may not be released properly. |
| 250 | If you want your threads to stop gracefully, make them non-daemonic and |
| 251 | use a suitable signalling mechanism such as an :class:`Event`. |
| 252 | |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 253 | There is a "main thread" object; this corresponds to the initial thread of |
| 254 | control in the Python program. It is not a daemon thread. |
| 255 | |
| 256 | There is the possibility that "dummy thread objects" are created. These are |
| 257 | thread objects corresponding to "alien threads", which are threads of control |
| 258 | started outside the threading module, such as directly from C code. Dummy |
| 259 | thread objects have limited functionality; they are always considered alive and |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 260 | daemonic, and cannot be :meth:`~Thread.join`\ ed. They are never deleted, |
| 261 | since it is impossible to detect the termination of alien threads. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 262 | |
| 263 | |
| 264 | .. class:: Thread(group=None, target=None, name=None, args=(), kwargs={}) |
| 265 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 266 | This constructor should always be called with keyword arguments. Arguments |
| 267 | are: |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 268 | |
| 269 | *group* should be ``None``; reserved for future extension when a |
| 270 | :class:`ThreadGroup` class is implemented. |
| 271 | |
| 272 | *target* is the callable object to be invoked by the :meth:`run` method. |
| 273 | Defaults to ``None``, meaning nothing is called. |
| 274 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 275 | *name* is the thread name. By default, a unique name is constructed of the |
| 276 | form "Thread-*N*" where *N* is a small decimal number. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 277 | |
| 278 | *args* is the argument tuple for the target invocation. Defaults to ``()``. |
| 279 | |
| 280 | *kwargs* is a dictionary of keyword arguments for the target invocation. |
| 281 | Defaults to ``{}``. |
| 282 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 283 | If the subclass overrides the constructor, it must make sure to invoke the |
| 284 | base class constructor (``Thread.__init__()``) before doing anything else to |
| 285 | the thread. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 286 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 287 | .. method:: start() |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 288 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 289 | Start the thread's activity. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 290 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 291 | It must be called at most once per thread object. It arranges for the |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 292 | object's :meth:`~Thread.run` method to be invoked in a separate thread |
| 293 | of control. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 294 | |
Brian Curtin | bd0c897 | 2011-01-31 19:35:02 +0000 | [diff] [blame] | 295 | This method will raise a :exc:`RuntimeError` if called more than once |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 296 | on the same thread object. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 297 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 298 | .. method:: run() |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 299 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 300 | Method representing the thread's activity. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 301 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 302 | You may override this method in a subclass. The standard :meth:`run` |
| 303 | method invokes the callable object passed to the object's constructor as |
| 304 | the *target* argument, if any, with sequential and keyword arguments taken |
| 305 | from the *args* and *kwargs* arguments, respectively. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 306 | |
Georg Brandl | 7f01a13 | 2009-09-16 15:58:14 +0000 | [diff] [blame] | 307 | .. method:: join(timeout=None) |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 308 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 309 | Wait until the thread terminates. This blocks the calling thread until |
| 310 | the thread whose :meth:`~Thread.join` method is called terminates -- either |
| 311 | normally or through an unhandled exception --, or until the optional |
| 312 | timeout occurs. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 313 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 314 | When the *timeout* argument is present and not ``None``, it should be a |
| 315 | floating point number specifying a timeout for the operation in seconds |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 316 | (or fractions thereof). As :meth:`~Thread.join` always returns ``None``, |
| 317 | you must call :meth:`~Thread.is_alive` after :meth:`~Thread.join` to |
| 318 | decide whether a timeout happened -- if the thread is still alive, the |
| 319 | :meth:`~Thread.join` call timed out. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 320 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 321 | When the *timeout* argument is not present or ``None``, the operation will |
| 322 | block until the thread terminates. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 323 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 324 | A thread can be :meth:`~Thread.join`\ ed many times. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 325 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 326 | :meth:`~Thread.join` raises a :exc:`RuntimeError` if an attempt is made |
| 327 | to join the current thread as that would cause a deadlock. It is also |
| 328 | an error to :meth:`~Thread.join` a thread before it has been started |
| 329 | and attempts to do so raise the same exception. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 330 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 331 | .. attribute:: name |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 332 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 333 | A string used for identification purposes only. It has no semantics. |
| 334 | Multiple threads may be given the same name. The initial name is set by |
| 335 | the constructor. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 336 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 337 | .. method:: getName() |
| 338 | setName() |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 339 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 340 | Old getter/setter API for :attr:`~Thread.name`; use it directly as a |
| 341 | property instead. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 342 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 343 | .. attribute:: ident |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 344 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 345 | The 'thread identifier' of this thread or ``None`` if the thread has not |
| 346 | been started. This is a nonzero integer. See the |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 347 | :func:`_thread.get_ident()` function. Thread identifiers may be recycled |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 348 | when a thread exits and another thread is created. The identifier is |
| 349 | available even after the thread has exited. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 350 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 351 | .. method:: is_alive() |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 352 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 353 | Return whether the thread is alive. |
Georg Brandl | 770b0be | 2009-01-02 20:10:05 +0000 | [diff] [blame] | 354 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 355 | This method returns ``True`` just before the :meth:`~Thread.run` method |
| 356 | starts until just after the :meth:`~Thread.run` method terminates. The |
| 357 | module function :func:`.enumerate` returns a list of all alive threads. |
Georg Brandl | 770b0be | 2009-01-02 20:10:05 +0000 | [diff] [blame] | 358 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 359 | .. attribute:: daemon |
Georg Brandl | 770b0be | 2009-01-02 20:10:05 +0000 | [diff] [blame] | 360 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 361 | A boolean value indicating whether this thread is a daemon thread (True) |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 362 | or not (False). This must be set before :meth:`~Thread.start` is called, |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 363 | otherwise :exc:`RuntimeError` is raised. Its initial value is inherited |
| 364 | from the creating thread; the main thread is not a daemon thread and |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 365 | therefore all threads created in the main thread default to |
| 366 | :attr:`~Thread.daemon` = ``False``. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 367 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 368 | The entire Python program exits when no alive non-daemon threads are left. |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 369 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 370 | .. method:: isDaemon() |
| 371 | setDaemon() |
Georg Brandl | a971c65 | 2008-11-07 09:39:56 +0000 | [diff] [blame] | 372 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 373 | Old getter/setter API for :attr:`~Thread.daemon`; use it directly as a |
| 374 | property instead. |
Georg Brandl | 770b0be | 2009-01-02 20:10:05 +0000 | [diff] [blame] | 375 | |
| 376 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 377 | .. _lock-objects: |
| 378 | |
| 379 | Lock Objects |
| 380 | ------------ |
| 381 | |
| 382 | A primitive lock is a synchronization primitive that is not owned by a |
| 383 | particular thread when locked. In Python, it is currently the lowest level |
Georg Brandl | 2067bfd | 2008-05-25 13:05:15 +0000 | [diff] [blame] | 384 | synchronization primitive available, implemented directly by the :mod:`_thread` |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 385 | extension module. |
| 386 | |
| 387 | A primitive lock is in one of two states, "locked" or "unlocked". It is created |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 388 | in the unlocked state. It has two basic methods, :meth:`~Lock.acquire` and |
| 389 | :meth:`~Lock.release`. When the state is unlocked, :meth:`~Lock.acquire` |
| 390 | changes the state to locked and returns immediately. When the state is locked, |
| 391 | :meth:`~Lock.acquire` blocks until a call to :meth:`~Lock.release` in another |
| 392 | thread changes it to unlocked, then the :meth:`~Lock.acquire` call resets it |
| 393 | to locked and returns. The :meth:`~Lock.release` method should only be |
| 394 | called in the locked state; it changes the state to unlocked and returns |
| 395 | immediately. If an attempt is made to release an unlocked lock, a |
| 396 | :exc:`RuntimeError` will be raised. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 397 | |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 398 | Locks also support the :ref:`context manager protocol <with-locks>`. |
| 399 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 400 | When more than one thread is blocked in :meth:`~Lock.acquire` waiting for the |
| 401 | state to turn to unlocked, only one thread proceeds when a :meth:`~Lock.release` |
| 402 | call resets the state to unlocked; which one of the waiting threads proceeds |
| 403 | is not defined, and may vary across implementations. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 404 | |
| 405 | All methods are executed atomically. |
| 406 | |
| 407 | |
Antoine Pitrou | 7c3e577 | 2010-04-14 15:44:10 +0000 | [diff] [blame] | 408 | .. method:: Lock.acquire(blocking=True, timeout=-1) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 409 | |
| 410 | Acquire a lock, blocking or non-blocking. |
| 411 | |
R David Murray | f7a6615 | 2012-05-17 09:13:30 -0400 | [diff] [blame] | 412 | When invoked with the *blocking* argument set to ``True`` (the default), |
| 413 | block until the lock is unlocked, then set it to locked and return ``True``. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 414 | |
R David Murray | f7a6615 | 2012-05-17 09:13:30 -0400 | [diff] [blame] | 415 | When invoked with the *blocking* argument set to ``False``, do not block. |
| 416 | If a call with *blocking* set to ``True`` would block, return ``False`` |
| 417 | immediately; otherwise, set the lock to locked and return ``True``. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 418 | |
Antoine Pitrou | 7c3e577 | 2010-04-14 15:44:10 +0000 | [diff] [blame] | 419 | When invoked with the floating-point *timeout* argument set to a positive |
| 420 | value, block for at most the number of seconds specified by *timeout* |
| 421 | and as long as the lock cannot be acquired. A negative *timeout* argument |
| 422 | specifies an unbounded wait. It is forbidden to specify a *timeout* |
| 423 | when *blocking* is false. |
| 424 | |
| 425 | The return value is ``True`` if the lock is acquired successfully, |
| 426 | ``False`` if not (for example if the *timeout* expired). |
| 427 | |
Antoine Pitrou | adbc009 | 2010-04-19 14:05:51 +0000 | [diff] [blame] | 428 | .. versionchanged:: 3.2 |
| 429 | The *timeout* parameter is new. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 430 | |
Antoine Pitrou | 810023d | 2010-12-15 22:59:16 +0000 | [diff] [blame] | 431 | .. versionchanged:: 3.2 |
| 432 | Lock acquires can now be interrupted by signals on POSIX. |
| 433 | |
Georg Brandl | 67b21b7 | 2010-08-17 15:07:14 +0000 | [diff] [blame] | 434 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 435 | .. method:: Lock.release() |
| 436 | |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 437 | Release a lock. This can be called from any thread, not only the thread |
| 438 | which has acquired the lock. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 439 | |
| 440 | When the lock is locked, reset it to unlocked, and return. If any other threads |
| 441 | are blocked waiting for the lock to become unlocked, allow exactly one of them |
| 442 | to proceed. |
| 443 | |
Sandro Tosi | fee3fc7 | 2012-04-05 22:51:54 +0200 | [diff] [blame] | 444 | When invoked on an unlocked lock, a :exc:`ThreadError` is raised. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 445 | |
| 446 | There is no return value. |
| 447 | |
| 448 | |
| 449 | .. _rlock-objects: |
| 450 | |
| 451 | RLock Objects |
| 452 | ------------- |
| 453 | |
| 454 | A reentrant lock is a synchronization primitive that may be acquired multiple |
| 455 | times by the same thread. Internally, it uses the concepts of "owning thread" |
| 456 | and "recursion level" in addition to the locked/unlocked state used by primitive |
| 457 | locks. In the locked state, some thread owns the lock; in the unlocked state, |
| 458 | no thread owns it. |
| 459 | |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 460 | To lock the lock, a thread calls its :meth:`~RLock.acquire` method; this |
| 461 | returns once the thread owns the lock. To unlock the lock, a thread calls |
| 462 | its :meth:`~Lock.release` method. :meth:`~Lock.acquire`/:meth:`~Lock.release` |
| 463 | call pairs may be nested; only the final :meth:`~Lock.release` (the |
| 464 | :meth:`~Lock.release` of the outermost pair) resets the lock to unlocked and |
| 465 | allows another thread blocked in :meth:`~Lock.acquire` to proceed. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 466 | |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 467 | Reentrant locks also support the :ref:`context manager protocol <with-locks>`. |
| 468 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 469 | |
Antoine Pitrou | 7c3e577 | 2010-04-14 15:44:10 +0000 | [diff] [blame] | 470 | .. method:: RLock.acquire(blocking=True, timeout=-1) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 471 | |
| 472 | Acquire a lock, blocking or non-blocking. |
| 473 | |
| 474 | When invoked without arguments: if this thread already owns the lock, increment |
| 475 | the recursion level by one, and return immediately. Otherwise, if another |
| 476 | thread owns the lock, block until the lock is unlocked. Once the lock is |
| 477 | unlocked (not owned by any thread), then grab ownership, set the recursion level |
| 478 | to one, and return. If more than one thread is blocked waiting until the lock |
| 479 | is unlocked, only one at a time will be able to grab ownership of the lock. |
| 480 | There is no return value in this case. |
| 481 | |
| 482 | When invoked with the *blocking* argument set to true, do the same thing as when |
| 483 | called without arguments, and return true. |
| 484 | |
| 485 | When invoked with the *blocking* argument set to false, do not block. If a call |
| 486 | without an argument would block, return false immediately; otherwise, do the |
| 487 | same thing as when called without arguments, and return true. |
| 488 | |
Antoine Pitrou | 7c3e577 | 2010-04-14 15:44:10 +0000 | [diff] [blame] | 489 | When invoked with the floating-point *timeout* argument set to a positive |
| 490 | value, block for at most the number of seconds specified by *timeout* |
| 491 | and as long as the lock cannot be acquired. Return true if the lock has |
| 492 | been acquired, false if the timeout has elapsed. |
| 493 | |
Antoine Pitrou | adbc009 | 2010-04-19 14:05:51 +0000 | [diff] [blame] | 494 | .. versionchanged:: 3.2 |
| 495 | The *timeout* parameter is new. |
| 496 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 497 | |
| 498 | .. method:: RLock.release() |
| 499 | |
| 500 | Release a lock, decrementing the recursion level. If after the decrement it is |
| 501 | zero, reset the lock to unlocked (not owned by any thread), and if any other |
| 502 | threads are blocked waiting for the lock to become unlocked, allow exactly one |
| 503 | of them to proceed. If after the decrement the recursion level is still |
| 504 | nonzero, the lock remains locked and owned by the calling thread. |
| 505 | |
| 506 | Only call this method when the calling thread owns the lock. A |
| 507 | :exc:`RuntimeError` is raised if this method is called when the lock is |
| 508 | unlocked. |
| 509 | |
| 510 | There is no return value. |
| 511 | |
| 512 | |
| 513 | .. _condition-objects: |
| 514 | |
| 515 | Condition Objects |
| 516 | ----------------- |
| 517 | |
| 518 | A condition variable is always associated with some kind of lock; this can be |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 519 | passed in or one will be created by default. Passing one in is useful when |
| 520 | several condition variables must share the same lock. The lock is part of |
| 521 | the condition object: you don't have to track it separately. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 522 | |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 523 | A condition variable obeys the :ref:`context manager protocol <with-locks>`: |
| 524 | using the ``with`` statement acquires the associated lock for the duration of |
| 525 | the enclosed block. The :meth:`~Condition.acquire` and |
| 526 | :meth:`~Condition.release` methods also call the corresponding methods of |
| 527 | the associated lock. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 528 | |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 529 | Other methods must be called with the associated lock held. The |
| 530 | :meth:`~Condition.wait` method releases the lock, and then blocks until |
| 531 | another thread awakens it by calling :meth:`~Condition.notify` or |
| 532 | :meth:`~Condition.notify_all`. Once awakened, :meth:`~Condition.wait` |
| 533 | re-acquires the lock and returns. It is also possible to specify a timeout. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 534 | |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 535 | The :meth:`~Condition.notify` method wakes up one of the threads waiting for |
| 536 | the condition variable, if any are waiting. The :meth:`~Condition.notify_all` |
| 537 | method wakes up all threads waiting for the condition variable. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 538 | |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 539 | Note: the :meth:`~Condition.notify` and :meth:`~Condition.notify_all` methods |
| 540 | don't release the lock; this means that the thread or threads awakened will |
| 541 | not return from their :meth:`~Condition.wait` call immediately, but only when |
| 542 | the thread that called :meth:`~Condition.notify` or :meth:`~Condition.notify_all` |
| 543 | finally relinquishes ownership of the lock. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 544 | |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 545 | |
| 546 | Usage |
| 547 | ^^^^^ |
| 548 | |
| 549 | The typical programming style using condition variables uses the lock to |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 550 | synchronize access to some shared state; threads that are interested in a |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 551 | particular change of state call :meth:`~Condition.wait` repeatedly until they |
| 552 | see the desired state, while threads that modify the state call |
| 553 | :meth:`~Condition.notify` or :meth:`~Condition.notify_all` when they change |
| 554 | the state in such a way that it could possibly be a desired state for one |
| 555 | of the waiters. For example, the following code is a generic |
| 556 | producer-consumer situation with unlimited buffer capacity:: |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 557 | |
| 558 | # Consume one item |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 559 | with cv: |
| 560 | while not an_item_is_available(): |
| 561 | cv.wait() |
| 562 | get_an_available_item() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 563 | |
| 564 | # Produce one item |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 565 | with cv: |
| 566 | make_an_item_available() |
Antoine Pitrou | f6cd9b2 | 2012-04-11 19:37:56 +0200 | [diff] [blame] | 567 | cv.notify() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 568 | |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 569 | The ``while`` loop checking for the application's condition is necessary |
| 570 | because :meth:`~Condition.wait` can return after an arbitrary long time, |
Antoine Pitrou | f6cd9b2 | 2012-04-11 19:37:56 +0200 | [diff] [blame] | 571 | and the condition which prompted the :meth:`~Condition.notify` call may |
| 572 | no longer hold true. This is inherent to multi-threaded programming. The |
| 573 | :meth:`~Condition.wait_for` method can be used to automate the condition |
| 574 | checking, and eases the computation of timeouts:: |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 575 | |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 576 | # Consume an item |
| 577 | with cv: |
| 578 | cv.wait_for(an_item_is_available) |
| 579 | get_an_available_item() |
Kristján Valur Jónsson | 6331520 | 2010-11-18 12:46:39 +0000 | [diff] [blame] | 580 | |
Antoine Pitrou | 126aef7 | 2012-04-10 22:24:05 +0200 | [diff] [blame] | 581 | To choose between :meth:`~Condition.notify` and :meth:`~Condition.notify_all`, |
| 582 | consider whether one state change can be interesting for only one or several |
| 583 | waiting threads. E.g. in a typical producer-consumer situation, adding one |
| 584 | item to the buffer only needs to wake up one consumer thread. |
| 585 | |
| 586 | |
| 587 | Interface |
| 588 | ^^^^^^^^^ |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 589 | |
Georg Brandl | 7f01a13 | 2009-09-16 15:58:14 +0000 | [diff] [blame] | 590 | .. class:: Condition(lock=None) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 591 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 592 | If the *lock* argument is given and not ``None``, it must be a :class:`Lock` |
| 593 | or :class:`RLock` object, and it is used as the underlying lock. Otherwise, |
| 594 | a new :class:`RLock` object is created and used as the underlying lock. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 595 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 596 | .. method:: acquire(*args) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 597 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 598 | Acquire the underlying lock. This method calls the corresponding method on |
| 599 | the underlying lock; the return value is whatever that method returns. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 600 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 601 | .. method:: release() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 602 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 603 | Release the underlying lock. This method calls the corresponding method on |
| 604 | the underlying lock; there is no return value. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 605 | |
Georg Brandl | 7f01a13 | 2009-09-16 15:58:14 +0000 | [diff] [blame] | 606 | .. method:: wait(timeout=None) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 607 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 608 | Wait until notified or until a timeout occurs. If the calling thread has |
| 609 | not acquired the lock when this method is called, a :exc:`RuntimeError` is |
| 610 | raised. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 611 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 612 | This method releases the underlying lock, and then blocks until it is |
| 613 | awakened by a :meth:`notify` or :meth:`notify_all` call for the same |
| 614 | condition variable in another thread, or until the optional timeout |
| 615 | occurs. Once awakened or timed out, it re-acquires the lock and returns. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 616 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 617 | When the *timeout* argument is present and not ``None``, it should be a |
| 618 | floating point number specifying a timeout for the operation in seconds |
| 619 | (or fractions thereof). |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 620 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 621 | When the underlying lock is an :class:`RLock`, it is not released using |
| 622 | its :meth:`release` method, since this may not actually unlock the lock |
| 623 | when it was acquired multiple times recursively. Instead, an internal |
| 624 | interface of the :class:`RLock` class is used, which really unlocks it |
| 625 | even when it has been recursively acquired several times. Another internal |
| 626 | interface is then used to restore the recursion level when the lock is |
| 627 | reacquired. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 628 | |
Georg Brandl | b9a4391 | 2010-10-28 09:03:20 +0000 | [diff] [blame] | 629 | The return value is ``True`` unless a given *timeout* expired, in which |
| 630 | case it is ``False``. |
| 631 | |
| 632 | .. versionchanged:: 3.2 |
| 633 | Previously, the method always returned ``None``. |
| 634 | |
Kristján Valur Jónsson | 6331520 | 2010-11-18 12:46:39 +0000 | [diff] [blame] | 635 | .. method:: wait_for(predicate, timeout=None) |
| 636 | |
| 637 | Wait until a condition evaluates to True. *predicate* should be a |
| 638 | callable which result will be interpreted as a boolean value. |
| 639 | A *timeout* may be provided giving the maximum time to wait. |
| 640 | |
| 641 | This utility method may call :meth:`wait` repeatedly until the predicate |
| 642 | is satisfied, or until a timeout occurs. The return value is |
| 643 | the last return value of the predicate and will evaluate to |
| 644 | ``False`` if the method timed out. |
| 645 | |
| 646 | Ignoring the timeout feature, calling this method is roughly equivalent to |
| 647 | writing:: |
| 648 | |
| 649 | while not predicate(): |
| 650 | cv.wait() |
| 651 | |
| 652 | Therefore, the same rules apply as with :meth:`wait`: The lock must be |
| 653 | held when called and is re-aquired on return. The predicate is evaluated |
| 654 | with the lock held. |
| 655 | |
Kristján Valur Jónsson | 6331520 | 2010-11-18 12:46:39 +0000 | [diff] [blame] | 656 | .. versionadded:: 3.2 |
| 657 | |
Eli Bendersky | d44af82 | 2011-11-12 20:44:25 +0200 | [diff] [blame] | 658 | .. method:: notify(n=1) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 659 | |
Eli Bendersky | d44af82 | 2011-11-12 20:44:25 +0200 | [diff] [blame] | 660 | By default, wake up one thread waiting on this condition, if any. If the |
| 661 | calling thread has not acquired the lock when this method is called, a |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 662 | :exc:`RuntimeError` is raised. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 663 | |
Eli Bendersky | d44af82 | 2011-11-12 20:44:25 +0200 | [diff] [blame] | 664 | This method wakes up at most *n* of the threads waiting for the condition |
| 665 | variable; it is a no-op if no threads are waiting. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 666 | |
Eli Bendersky | d44af82 | 2011-11-12 20:44:25 +0200 | [diff] [blame] | 667 | The current implementation wakes up exactly *n* threads, if at least *n* |
| 668 | threads are waiting. However, it's not safe to rely on this behavior. |
| 669 | A future, optimized implementation may occasionally wake up more than |
| 670 | *n* threads. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 671 | |
Eli Bendersky | d44af82 | 2011-11-12 20:44:25 +0200 | [diff] [blame] | 672 | Note: an awakened thread does not actually return from its :meth:`wait` |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 673 | call until it can reacquire the lock. Since :meth:`notify` does not |
| 674 | release the lock, its caller should. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 675 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 676 | .. method:: notify_all() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 677 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 678 | Wake up all threads waiting on this condition. This method acts like |
| 679 | :meth:`notify`, but wakes up all waiting threads instead of one. If the |
| 680 | calling thread has not acquired the lock when this method is called, a |
| 681 | :exc:`RuntimeError` is raised. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 682 | |
| 683 | |
| 684 | .. _semaphore-objects: |
| 685 | |
| 686 | Semaphore Objects |
| 687 | ----------------- |
| 688 | |
| 689 | This is one of the oldest synchronization primitives in the history of computer |
| 690 | science, invented by the early Dutch computer scientist Edsger W. Dijkstra (he |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 691 | used the names ``P()`` and ``V()`` instead of :meth:`~Semaphore.acquire` and |
| 692 | :meth:`~Semaphore.release`). |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 693 | |
| 694 | A semaphore manages an internal counter which is decremented by each |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 695 | :meth:`~Semaphore.acquire` call and incremented by each :meth:`~Semaphore.release` |
| 696 | call. The counter can never go below zero; when :meth:`~Semaphore.acquire` |
| 697 | finds that it is zero, it blocks, waiting until some other thread calls |
| 698 | :meth:`~Semaphore.release`. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 699 | |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 700 | Semaphores also support the :ref:`context manager protocol <with-locks>`. |
| 701 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 702 | |
Georg Brandl | 7f01a13 | 2009-09-16 15:58:14 +0000 | [diff] [blame] | 703 | .. class:: Semaphore(value=1) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 704 | |
| 705 | The optional argument gives the initial *value* for the internal counter; it |
| 706 | defaults to ``1``. If the *value* given is less than 0, :exc:`ValueError` is |
| 707 | raised. |
| 708 | |
Antoine Pitrou | 0454af9 | 2010-04-17 23:51:58 +0000 | [diff] [blame] | 709 | .. method:: acquire(blocking=True, timeout=None) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 710 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 711 | Acquire a semaphore. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 712 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 713 | When invoked without arguments: if the internal counter is larger than |
| 714 | zero on entry, decrement it by one and return immediately. If it is zero |
| 715 | on entry, block, waiting until some other thread has called |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 716 | :meth:`~Semaphore.release` to make it larger than zero. This is done |
| 717 | with proper interlocking so that if multiple :meth:`acquire` calls are |
| 718 | blocked, :meth:`~Semaphore.release` will wake exactly one of them up. |
| 719 | The implementation may pick one at random, so the order in which |
| 720 | blocked threads are awakened should not be relied on. Returns |
| 721 | true (or blocks indefinitely). |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 722 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 723 | When invoked with *blocking* set to false, do not block. If a call |
Antoine Pitrou | 0454af9 | 2010-04-17 23:51:58 +0000 | [diff] [blame] | 724 | without an argument would block, return false immediately; otherwise, |
| 725 | do the same thing as when called without arguments, and return true. |
| 726 | |
| 727 | When invoked with a *timeout* other than None, it will block for at |
| 728 | most *timeout* seconds. If acquire does not complete successfully in |
| 729 | that interval, return false. Return true otherwise. |
| 730 | |
| 731 | .. versionchanged:: 3.2 |
| 732 | The *timeout* parameter is new. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 733 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 734 | .. method:: release() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 735 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 736 | Release a semaphore, incrementing the internal counter by one. When it |
| 737 | was zero on entry and another thread is waiting for it to become larger |
| 738 | than zero again, wake up that thread. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 739 | |
| 740 | |
| 741 | .. _semaphore-examples: |
| 742 | |
| 743 | :class:`Semaphore` Example |
| 744 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 745 | |
| 746 | Semaphores are often used to guard resources with limited capacity, for example, |
Georg Brandl | a572476 | 2011-01-06 19:28:18 +0000 | [diff] [blame] | 747 | a database server. In any situation where the size of the resource is fixed, |
| 748 | you should use a bounded semaphore. Before spawning any worker threads, your |
| 749 | main thread would initialize the semaphore:: |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 750 | |
| 751 | maxconnections = 5 |
| 752 | ... |
| 753 | pool_sema = BoundedSemaphore(value=maxconnections) |
| 754 | |
| 755 | Once spawned, worker threads call the semaphore's acquire and release methods |
| 756 | when they need to connect to the server:: |
| 757 | |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 758 | with pool_sema: |
| 759 | conn = connectdb() |
| 760 | try: |
| 761 | ... use connection ... |
| 762 | finally: |
| 763 | conn.close() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 764 | |
| 765 | The use of a bounded semaphore reduces the chance that a programming error which |
| 766 | causes the semaphore to be released more than it's acquired will go undetected. |
| 767 | |
| 768 | |
| 769 | .. _event-objects: |
| 770 | |
| 771 | Event Objects |
| 772 | ------------- |
| 773 | |
| 774 | This is one of the simplest mechanisms for communication between threads: one |
| 775 | thread signals an event and other threads wait for it. |
| 776 | |
| 777 | An event object manages an internal flag that can be set to true with the |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 778 | :meth:`~Event.set` method and reset to false with the :meth:`~Event.clear` |
| 779 | method. The :meth:`~Event.wait` method blocks until the flag is true. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 780 | |
| 781 | |
| 782 | .. class:: Event() |
| 783 | |
| 784 | The internal flag is initially false. |
| 785 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 786 | .. method:: is_set() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 787 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 788 | Return true if and only if the internal flag is true. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 789 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 790 | .. method:: set() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 791 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 792 | Set the internal flag to true. All threads waiting for it to become true |
| 793 | are awakened. Threads that call :meth:`wait` once the flag is true will |
| 794 | not block at all. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 795 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 796 | .. method:: clear() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 797 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 798 | Reset the internal flag to false. Subsequently, threads calling |
Georg Brandl | 502d9a5 | 2009-07-26 15:02:41 +0000 | [diff] [blame] | 799 | :meth:`wait` will block until :meth:`.set` is called to set the internal |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 800 | flag to true again. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 801 | |
Georg Brandl | 7f01a13 | 2009-09-16 15:58:14 +0000 | [diff] [blame] | 802 | .. method:: wait(timeout=None) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 803 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 804 | Block until the internal flag is true. If the internal flag is true on |
| 805 | entry, return immediately. Otherwise, block until another thread calls |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 806 | :meth:`.set` to set the flag to true, or until the optional timeout occurs. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 807 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 808 | When the timeout argument is present and not ``None``, it should be a |
| 809 | floating point number specifying a timeout for the operation in seconds |
| 810 | (or fractions thereof). |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 811 | |
Charles-François Natali | ded0348 | 2012-01-07 18:24:56 +0100 | [diff] [blame] | 812 | This method returns true if and only if the internal flag has been set to |
| 813 | true, either before the wait call or after the wait starts, so it will |
| 814 | always return ``True`` except if a timeout is given and the operation |
| 815 | times out. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 816 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 817 | .. versionchanged:: 3.1 |
| 818 | Previously, the method always returned ``None``. |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 819 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 820 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 821 | .. _timer-objects: |
| 822 | |
| 823 | Timer Objects |
| 824 | ------------- |
| 825 | |
| 826 | This class represents an action that should be run only after a certain amount |
| 827 | of time has passed --- a timer. :class:`Timer` is a subclass of :class:`Thread` |
| 828 | and as such also functions as an example of creating custom threads. |
| 829 | |
| 830 | Timers are started, as with threads, by calling their :meth:`start` method. The |
| 831 | timer can be stopped (before its action has begun) by calling the :meth:`cancel` |
| 832 | method. The interval the timer will wait before executing its action may not be |
| 833 | exactly the same as the interval specified by the user. |
| 834 | |
| 835 | For example:: |
| 836 | |
| 837 | def hello(): |
Collin Winter | c79461b | 2007-09-01 23:34:30 +0000 | [diff] [blame] | 838 | print("hello, world") |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 839 | |
| 840 | t = Timer(30.0, hello) |
| 841 | t.start() # after 30 seconds, "hello, world" will be printed |
| 842 | |
| 843 | |
| 844 | .. class:: Timer(interval, function, args=[], kwargs={}) |
| 845 | |
| 846 | Create a timer that will run *function* with arguments *args* and keyword |
| 847 | arguments *kwargs*, after *interval* seconds have passed. |
| 848 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 849 | .. method:: cancel() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 850 | |
Georg Brandl | 7a72b3a | 2009-07-26 14:48:09 +0000 | [diff] [blame] | 851 | Stop the timer, and cancel the execution of the timer's action. This will |
| 852 | only work if the timer is still in its waiting stage. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 853 | |
| 854 | |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 855 | Barrier Objects |
| 856 | --------------- |
| 857 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 858 | .. versionadded:: 3.2 |
| 859 | |
| 860 | This class provides a simple synchronization primitive for use by a fixed number |
| 861 | of threads that need to wait for each other. Each of the threads tries to pass |
Antoine Pitrou | 2c9f104 | 2012-04-10 22:35:53 +0200 | [diff] [blame] | 862 | the barrier by calling the :meth:`~Barrier.wait` method and will block until |
| 863 | all of the threads have made the call. At this points, the threads are released |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 864 | simultanously. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 865 | |
| 866 | The barrier can be reused any number of times for the same number of threads. |
| 867 | |
| 868 | As an example, here is a simple way to synchronize a client and server thread:: |
| 869 | |
| 870 | b = Barrier(2, timeout=5) |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 871 | |
| 872 | def server(): |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 873 | start_server() |
| 874 | b.wait() |
| 875 | while True: |
| 876 | connection = accept_connection() |
| 877 | process_server_connection(connection) |
| 878 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 879 | def client(): |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 880 | b.wait() |
| 881 | while True: |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 882 | connection = make_connection() |
| 883 | process_client_connection(connection) |
| 884 | |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 885 | |
| 886 | .. class:: Barrier(parties, action=None, timeout=None) |
| 887 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 888 | Create a barrier object for *parties* number of threads. An *action*, when |
| 889 | provided, is a callable to be called by one of the threads when they are |
| 890 | released. *timeout* is the default timeout value if none is specified for |
| 891 | the :meth:`wait` method. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 892 | |
| 893 | .. method:: wait(timeout=None) |
| 894 | |
| 895 | Pass the barrier. When all the threads party to the barrier have called |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 896 | this function, they are all released simultaneously. If a *timeout* is |
Ezio Melotti | e130a52 | 2011-10-19 10:58:56 +0300 | [diff] [blame] | 897 | provided, it is used in preference to any that was supplied to the class |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 898 | constructor. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 899 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 900 | The return value is an integer in the range 0 to *parties* -- 1, different |
Raymond Hettinger | 5cee47f | 2011-01-11 19:59:46 +0000 | [diff] [blame] | 901 | for each thread. This can be used to select a thread to do some special |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 902 | housekeeping, e.g.:: |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 903 | |
| 904 | i = barrier.wait() |
| 905 | if i == 0: |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 906 | # Only one thread needs to print this |
| 907 | print("passed the barrier") |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 908 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 909 | If an *action* was provided to the constructor, one of the threads will |
| 910 | have called it prior to being released. Should this call raise an error, |
| 911 | the barrier is put into the broken state. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 912 | |
| 913 | If the call times out, the barrier is put into the broken state. |
| 914 | |
| 915 | This method may raise a :class:`BrokenBarrierError` exception if the |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 916 | barrier is broken or reset while a thread is waiting. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 917 | |
| 918 | .. method:: reset() |
| 919 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 920 | Return the barrier to the default, empty state. Any threads waiting on it |
| 921 | will receive the :class:`BrokenBarrierError` exception. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 922 | |
| 923 | Note that using this function may can require some external |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 924 | synchronization if there are other threads whose state is unknown. If a |
| 925 | barrier is broken it may be better to just leave it and create a new one. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 926 | |
| 927 | .. method:: abort() |
| 928 | |
| 929 | Put the barrier into a broken state. This causes any active or future |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 930 | calls to :meth:`wait` to fail with the :class:`BrokenBarrierError`. Use |
| 931 | this for example if one of the needs to abort, to avoid deadlocking the |
| 932 | application. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 933 | |
| 934 | It may be preferable to simply create the barrier with a sensible |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 935 | *timeout* value to automatically guard against one of the threads going |
| 936 | awry. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 937 | |
| 938 | .. attribute:: parties |
| 939 | |
| 940 | The number of threads required to pass the barrier. |
| 941 | |
| 942 | .. attribute:: n_waiting |
| 943 | |
| 944 | The number of threads currently waiting in the barrier. |
| 945 | |
| 946 | .. attribute:: broken |
| 947 | |
| 948 | A boolean that is ``True`` if the barrier is in the broken state. |
| 949 | |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 950 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 951 | .. exception:: BrokenBarrierError |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 952 | |
Georg Brandl | 5bc1686 | 2010-10-28 13:07:50 +0000 | [diff] [blame] | 953 | This exception, a subclass of :exc:`RuntimeError`, is raised when the |
| 954 | :class:`Barrier` object is reset or broken. |
Kristján Valur Jónsson | 3be0003 | 2010-10-28 09:43:10 +0000 | [diff] [blame] | 955 | |
| 956 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 957 | .. _with-locks: |
| 958 | |
| 959 | Using locks, conditions, and semaphores in the :keyword:`with` statement |
| 960 | ------------------------------------------------------------------------ |
| 961 | |
| 962 | All of the objects provided by this module that have :meth:`acquire` and |
| 963 | :meth:`release` methods can be used as context managers for a :keyword:`with` |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 964 | statement. The :meth:`acquire` method will be called when the block is |
| 965 | entered, and :meth:`release` will be called when the block is exited. Hence, |
| 966 | the following snippet:: |
| 967 | |
| 968 | with some_lock: |
| 969 | # do something... |
| 970 | |
| 971 | is equivalent to:: |
| 972 | |
| 973 | some_lock.acquire() |
| 974 | try: |
| 975 | # do something... |
| 976 | finally: |
| 977 | some_lock.release() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 978 | |
| 979 | Currently, :class:`Lock`, :class:`RLock`, :class:`Condition`, |
| 980 | :class:`Semaphore`, and :class:`BoundedSemaphore` objects may be used as |
Antoine Pitrou | b96a354 | 2012-04-10 22:47:55 +0200 | [diff] [blame] | 981 | :keyword:`with` statement context managers. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 982 | |
Christian Heimes | dd15f6c | 2008-03-16 00:07:10 +0000 | [diff] [blame] | 983 | |
| 984 | .. _threaded-imports: |
| 985 | |
| 986 | Importing in threaded code |
| 987 | -------------------------- |
| 988 | |
Georg Brandl | f285bcc | 2010-10-19 21:07:16 +0000 | [diff] [blame] | 989 | While the import machinery is thread-safe, there are two key restrictions on |
| 990 | threaded imports due to inherent limitations in the way that thread-safety is |
| 991 | provided: |
Christian Heimes | dd15f6c | 2008-03-16 00:07:10 +0000 | [diff] [blame] | 992 | |
| 993 | * Firstly, other than in the main module, an import should not have the |
| 994 | side effect of spawning a new thread and then waiting for that thread in |
| 995 | any way. Failing to abide by this restriction can lead to a deadlock if |
| 996 | the spawned thread directly or indirectly attempts to import a module. |
| 997 | * Secondly, all import attempts must be completed before the interpreter |
| 998 | starts shutting itself down. This can be most easily achieved by only |
| 999 | performing imports from non-daemon threads created through the threading |
| 1000 | module. Daemon threads and threads created directly with the thread |
| 1001 | module will require some other form of synchronization to ensure they do |
| 1002 | not attempt imports after system shutdown has commenced. Failure to |
| 1003 | abide by this restriction will lead to intermittent exceptions and |
| 1004 | crashes during interpreter shutdown (as the late imports attempt to |
| 1005 | access machinery which is no longer in a valid state). |