QReadWriteLock#

The QReadWriteLock class provides read-write locking. More…

Synopsis#

Functions#

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

Warning

This section contains snippets that were automatically translated from C++ to Python and may contain errors.

A read-write lock is a synchronization tool for protecting resources that can be accessed for reading and writing. This type of lock is useful if you want to allow multiple threads to have simultaneous read-only access, but as soon as one thread wants to write to the resource, all other threads must be blocked until the writing is complete.

In many cases, QReadWriteLock is a direct competitor to QMutex . QReadWriteLock is a good choice if there are many concurrent reads and writing occurs infrequently.

Example:

lock = QReadWriteLock()
def run(self):

    ...
    lock.lockForRead()
    read_file()
    lock.unlock()
    ...

def run(self):

    ...
    lock.lockForWrite()
    write_file()
    lock.unlock()
    ...

To ensure that writers aren’t blocked forever by readers, readers attempting to obtain a lock will not succeed if there is a blocked writer waiting for access, even if the lock is currently only accessed by other readers. Also, if the lock is accessed by a writer and another writer comes in, that writer will have priority over any readers that might also be waiting.

Like QMutex , a QReadWriteLock can be recursively locked by the same thread when constructed with Recursive as RecursionMode . In such cases, unlock() must be called the same number of times lockForWrite() or lockForRead() was called. Note that the lock type cannot be changed when trying to lock recursively, i.e. it is not possible to lock for reading in a thread that already has locked for writing (and vice versa).

class PySide6.QtCore.QReadWriteLock([recursionMode=QReadWriteLock.RecursionMode.NonRecursive])#
Parameters:

recursionMode – RecursionMode

Constructs a QReadWriteLock object in the given recursionMode.

The default recursion mode is NonRecursive .

See also

lockForRead() lockForWrite() RecursionMode

PySide6.QtCore.QReadWriteLock.RecursionMode#

Constant

Description

QReadWriteLock.Recursive

In this mode, a thread can lock the same QReadWriteLock multiple times. The QReadWriteLock won’t be unlocked until a corresponding number of unlock() calls have been made.

QReadWriteLock.NonRecursive

In this mode, a thread may only lock a QReadWriteLock once.

See also

QReadWriteLock()

PySide6.QtCore.QReadWriteLock.lockForRead()#

Locks the lock for reading. This function will block the current thread if another thread has locked for writing.

It is not possible to lock for read if the thread already has locked for write.

PySide6.QtCore.QReadWriteLock.lockForWrite()#

Locks the lock for writing. This function will block the current thread if another thread (including the current) has locked for reading or writing (unless the lock has been created using the Recursive mode).

It is not possible to lock for write if the thread already has locked for read.

PySide6.QtCore.QReadWriteLock.tryLockForRead([timeout={}])#
Parameters:

timeout – PySide6.QtCore.QDeadlineTimer

Return type:

bool

This is an overloaded function.

Attempts to lock for reading. This function returns true if the lock was obtained; otherwise it returns false. If another thread has locked for writing, this function will wait until timeout expires for the lock to become available.

If the lock was obtained, the lock must be unlocked with unlock() before another thread can successfully lock it for writing.

It is not possible to lock for read if the thread already has locked for write.

PySide6.QtCore.QReadWriteLock.tryLockForRead(timeout)
Parameters:

timeout – int

Return type:

bool

Attempts to lock for reading. This function returns true if the lock was obtained; otherwise it returns false. If another thread has locked for writing, this function will wait for at most timeout milliseconds for the lock to become available.

Note: Passing a negative number as the timeout is equivalent to calling lockForRead() , i.e. this function will wait forever until lock can be locked for reading when timeout is negative.

If the lock was obtained, the lock must be unlocked with unlock() before another thread can successfully lock it for writing.

It is not possible to lock for read if the thread already has locked for write.

PySide6.QtCore.QReadWriteLock.tryLockForWrite([timeout={}])#
Parameters:

timeout – PySide6.QtCore.QDeadlineTimer

Return type:

bool

This is an overloaded function.

Attempts to lock for writing. This function returns true if the lock was obtained; otherwise it returns false. If another thread has locked for reading or writing, this function will wait until timeout expires for the lock to become available.

If the lock was obtained, the lock must be unlocked with unlock() before another thread can successfully lock it.

It is not possible to lock for write if the thread already has locked for read.

PySide6.QtCore.QReadWriteLock.tryLockForWrite(timeout)
Parameters:

timeout – int

Return type:

bool

Attempts to lock for writing. This function returns true if the lock was obtained; otherwise it returns false. If another thread has locked for reading or writing, this function will wait for at most timeout milliseconds for the lock to become available.

Note: Passing a negative number as the timeout is equivalent to calling lockForWrite() , i.e. this function will wait forever until lock can be locked for writing when timeout is negative.

If the lock was obtained, the lock must be unlocked with unlock() before another thread can successfully lock it.

It is not possible to lock for write if the thread already has locked for read.

PySide6.QtCore.QReadWriteLock.unlock()#

Unlocks the lock.

Attempting to unlock a lock that is not locked is an error, and will result in program termination.