The PySide.QtCore.QThread class provides platform-independent threads.
A PySide.QtCore.QThread represents a separate thread of control within the program; it shares data with all the other threads within the process but executes independently in the way that a separate program does on a multitasking operating system. Instead of starting in main() , QThreads begin executing in PySide.QtCore.QThread.run() . By default, PySide.QtCore.QThread.run() starts the event loop by calling exec() (see below). To create your own threads, subclass PySide.QtCore.QThread and reimplement PySide.QtCore.QThread.run() . For example:
class MyThread (QThread): def run(): socket = QTcpSocket() # connect QTcpSocket's signals somewhere meaningful # ... socket.connectToHost(hostName, portNumber) self.exec_()This will create a PySide.QtNetwork.QTcpSocket in the thread and then execute the thread’s event loop. Use the PySide.QtCore.QThread.start() method to begin execution. Execution ends when you return from PySide.QtCore.QThread.run() , just as an application does when it leaves main(). PySide.QtCore.QThread will notifiy you via a signal when the thread is PySide.QtCore.QThread.started() , PySide.QtCore.QThread.finished() , and PySide.QtCore.QThread.terminated() , or you can use PySide.QtCore.QThread.isFinished() and PySide.QtCore.QThread.isRunning() to query the state of the thread. Use PySide.QtCore.QThread.wait() to block until the thread has finished execution.
Each thread gets its own stack from the operating system. The operating system also determines the default size of the stack. You can use PySide.QtCore.QThread.setStackSize() to set a custom stack size.
Each PySide.QtCore.QThread can have its own event loop. You can start the event loop by calling exec() ; you can stop it by calling PySide.QtCore.QThread.exit() or PySide.QtCore.QThread.quit() . Having an event loop in a thread makes it possible to connect signals from other threads to slots in this thread, using a mechanism called queued connections . It also makes it possible to use classes that require the event loop, such as PySide.QtCore.QTimer and PySide.QtNetwork.QTcpSocket , in the thread. Note, however, that it is not possible to use any widget classes in the thread.
In extreme cases, you may want to forcibly PySide.QtCore.QThread.terminate() an executing thread. However, doing so is dangerous and discouraged. Please read the documentation for PySide.QtCore.QThread.terminate() and PySide.QtCore.QThread.setTerminationEnabled() for detailed information.
The static functions PySide.QtCore.QThread.currentThreadId() and PySide.QtCore.QThread.currentThread() return identifiers for the currently executing thread. The former returns a platform specific ID for the thread; the latter returns a PySide.QtCore.QThread pointer.
PySide.QtCore.QThread also provides platform independent sleep functions in varying resolutions. Use PySide.QtCore.QThread.sleep() for full second resolution, PySide.QtCore.QThread.msleep() for millisecond resolution, and PySide.QtCore.QThread.usleep() for microsecond resolution.
See also
Thread Support in Qt QThreadStorage PySide.QtCore.QMutex PySide.QtCore.QSemaphore PySide.QtCore.QWaitCondition Mandelbrot Example Semaphores Example Wait Conditions Example
Parameters: | parent – PySide.QtCore.QObject |
---|
Constructs a new thread with the given parent . The thread does not begin executing until PySide.QtCore.QThread.start() is called.
See also
This enum type indicates how the operating system should schedule newly created threads.
Constant | Description |
---|---|
QThread.IdlePriority | scheduled only when no other threads are running. |
QThread.LowestPriority | scheduled less often than LowPriority . |
QThread.LowPriority | scheduled less often than NormalPriority . |
QThread.NormalPriority | the default priority of the operating system. |
QThread.HighPriority | scheduled more often than NormalPriority . |
QThread.HighestPriority | scheduled more often than HighPriority . |
QThread.TimeCriticalPriority | scheduled as often as possible. |
QThread.InheritPriority | use the same priority as the creating thread. This is the default. |
Return type: | PySide.QtCore.QThread |
---|
Returns a pointer to a PySide.QtCore.QThread which represents the currently executing thread.
Return type: | PySide.QtCore.Qt::HANDLE |
---|
Returns the thread handle of the currently executing thread.
Warning
The handle returned by this function is used for internal purposes and should not be used in any application code.
Warning
On Windows, the returned value is a pseudo-handle for the current thread. It can’t be used for numerical comparison. i.e., this function returns the DWORD (Windows-Thread ID) returned by the Win32 function getCurrentThreadId(), not the HANDLE (Windows-Thread HANDLE) returned by the Win32 function getCurrentThread().
Return type: | PySide.QtCore.int |
---|
Enters the event loop and waits until PySide.QtCore.QThread.exit() is called, returning the value that was passed to PySide.QtCore.QThread.exit() . The value returned is 0 if PySide.QtCore.QThread.exit() is called via PySide.QtCore.QThread.quit() .
It is necessary to call this function to start event handling.
Parameters: | retcode – PySide.QtCore.int |
---|
Tells the thread’s event loop to exit with a return code.
After calling this function, the thread leaves the event loop and returns from the call to QEventLoop.exec() . The QEventLoop.exec() function returns returnCode .
By convention, a returnCode of 0 means success, any non-zero value indicates an error.
Note that unlike the C library function of the same name, this function does return to the caller – it is event processing that stops.
This function does nothing if the thread does not have an event loop.
Return type: | PySide.QtCore.int |
---|
Returns the ideal number of threads that can be run on the system. This is done querying the number of processor cores, both real and logical, in the system. This function returns -1 if the number of processor cores could not be detected.
Return type: | PySide.QtCore.bool |
---|
Returns true if the thread is finished; otherwise returns false.
See also
Return type: | PySide.QtCore.bool |
---|
Returns true if the thread is running; otherwise returns false.
See also
Parameters: | arg__1 – long |
---|
Causes the current thread to sleep for msecs milliseconds.
Return type: | PySide.QtCore.QThread.Priority |
---|
Returns the priority for a running thread. If the thread is not running, this function returns InheritPriority .
See also
QThread.Priority PySide.QtCore.QThread.setPriority() PySide.QtCore.QThread.start()
Tells the thread’s event loop to exit with return code 0 (success). Equivalent to calling QThread::exit(0).
This function does nothing if the thread does not have an event loop.
The starting point for the thread. After calling PySide.QtCore.QThread.start() , the newly created thread calls this function. The default implementation simply calls exec() .
You can reimplemented this function to do other useful work. Returning from this method will end the execution of the thread.
Parameters: | priority – PySide.QtCore.QThread.Priority |
---|
This function sets the priority for a running thread. If the thread is not running, this function does nothing and returns immediately. Use PySide.QtCore.QThread.start() to start a thread with a specific priority.
The priority argument can be any value in the QThread::Priority enum except for InheritPriorty .
The effect of the priority parameter is dependent on the operating system’s scheduling policy. In particular, the priority will be ignored on systems that do not support thread priorities (such as on Linux, see http://linux.die.net/man/2/sched_setscheduler for more details).
See also
QThread.Priority PySide.QtCore.QThread.priority() PySide.QtCore.QThread.start()
Parameters: | stackSize – PySide.QtCore.uint |
---|
Sets the maximum stack size for the thread to stackSize . If stackSize is greater than zero, the maximum stack size is set to stackSize bytes, otherwise the maximum stack size is automatically determined by the operating system.
Warning
Most operating systems place minimum and maximum limits on thread stack sizes. The thread will fail to start if the stack size is outside these limits.
See also
Parameters: | enabled – PySide.QtCore.bool |
---|
Enables or disables termination of the current thread based on the enabled parameter. The thread must have been started by PySide.QtCore.QThread .
When enabled is false, termination is disabled. Future calls to QThread.terminate() will return immediately without effect. Instead, the termination is deferred until termination is enabled.
When enabled is true, termination is enabled. Future calls to QThread.terminate() will terminate the thread normally. If termination has been deferred (i.e. QThread.terminate() was called with termination disabled), this function will terminate the calling thread immediately . Note that this function will not return in this case.
See also
Parameters: | arg__1 – long |
---|
Forces the current thread to sleep for secs seconds.
Return type: | PySide.QtCore.uint |
---|
Returns the maximum stack size for the thread (if set with PySide.QtCore.QThread.setStackSize() ); otherwise returns zero.
See also
Parameters: | priority – PySide.QtCore.QThread.Priority |
---|
Begins execution of the thread by calling PySide.QtCore.QThread.run() , which should be reimplemented in a PySide.QtCore.QThread subclass to contain your code. The operating system will schedule the thread according to the priority parameter. If the thread is already running, this function does nothing.
The effect of the priority parameter is dependent on the operating system’s scheduling policy. In particular, the priority will be ignored on systems that do not support thread priorities (such as on Linux, see http://linux.die.net/man/2/sched_setscheduler for more details).
Terminates the execution of the thread. The thread may or may not be terminated immediately, depending on the operating systems scheduling policies. Use QThread.wait() after PySide.QtCore.QThread.terminate() for synchronous termination.
When the thread is terminated, all threads waiting for the thread to finish will be woken up.
Warning
This function is dangerous and its use is discouraged. The thread can be terminated at any point in its code path. Threads can be terminated while modifying data. There is no chance for the thread to clean up after itself, unlock any held mutexes, etc. In short, use this function only if absolutely necessary.
Termination can be explicitly enabled or disabled by calling QThread.setTerminationEnabled() . Calling this function while termination is disabled results in the termination being deferred, until termination is re-enabled. See the documentation of QThread.setTerminationEnabled() for more information.
Parameters: | arg__1 – long |
---|
Causes the current thread to sleep for usecs microseconds.
Parameters: | time – long |
---|---|
Return type: | PySide.QtCore.bool |
Blocks the thread until either of these conditions is met:
This provides similar functionality to the POSIX pthread_join() function.
Yields execution of the current thread to another runnable thread, if any. Note that the operating system decides to which thread to switch.