Lines Matching +full:threads +full:- +full:posix

1 :mod:`_thread` --- Low-level threading API
5    :synopsis: Low-level threading API.
8    single: light-weight processes
9    single: processes, light-weight
13 --------------
15 This module provides low-level primitives for working with multiple threads
16 (also called :dfn:`light-weight processes` or :dfn:`tasks`) --- multiple threads of
19 The :mod:`threading` module provides an easier to use and higher-level
24    pair: threads; POSIX
33    Raised on thread-specific errors.
36       This is now a synonym of the built-in :exc:`RuntimeError`.
55    printed and then the thread exits (but other threads continue to run).
94       Exit all threads and report the value of the integer argument
97       or in other threads, is not executed.
110    be used e.g. to index a dictionary of thread-specific data.  Thread identifiers
117    This is a non-negative integer.
118    Its value may be used to uniquely identify this particular thread system-wide
128    Return the thread stack size used when creating new threads.  The optional
130    threads, and must be 0 (use platform or configured default) or a positive
139    memory page size - platform documentation should be referred to for more
145       Unix platforms with POSIX threads support.
160 .. method:: lock.acquire(blocking=True, timeout=-1)
164    time can acquire a lock --- that's their reason for existence).
171    If the floating-point *timeout* argument is present and positive, it
183       Lock acquires can now be interrupted by signals on POSIX.
211 * Threads interact strangely with interrupts: the :exc:`KeyboardInterrupt`
218 * It is not possible to interrupt the :meth:`acquire` method on a lock --- the
221 * When the main thread exits, it is system defined whether the other threads