PySide6.QtCore.QFileSystemWatcher¶
- class QFileSystemWatcher¶
The
QFileSystemWatcher
class provides an interface for monitoring files and directories for modifications. More…Synopsis¶
Methods¶
def
__init__()
def
addPath()
def
addPaths()
def
directories()
def
files()
def
removePath()
def
removePaths()
Signals¶
def
fileChanged()
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¶
QFileSystemWatcher
monitors the file system for changes to files and directories by watching a list of specified paths.Call
addPath()
to watch a particular file or directory. Multiple paths can be added using theaddPaths()
function. Existing paths can be removed by using theremovePath()
andremovePaths()
functions.QFileSystemWatcher
examines each path added to it. Files that have been added to theQFileSystemWatcher
can be accessed using thefiles()
function, and directories using thedirectories()
function.The
fileChanged()
signal is emitted when a file has been modified, renamed or removed from disk. Similarly, thedirectoryChanged()
signal is emitted when a directory or its contents is modified or removed. Note thatQFileSystemWatcher
stops monitoring files once they have been renamed or removed from disk, and directories once they have been removed from disk.Notes:
On systems running a Linux kernel without inotify support, file systems that contain watched paths cannot be unmounted.
The act of monitoring files and directories for modifications consumes system resources. This implies there is a limit to the number of files and directories your process can monitor simultaneously. On all BSD variants, for example, an open file descriptor is required for each monitored file. Some system limits the number of open file descriptors to 256 by default. This means that
addPath()
andaddPaths()
will fail if your process tries to add more than 256 files or directories to the file system monitor. Also note that your process may have other file descriptors open in addition to the ones for files being monitored, and these other open descriptors also count in the total. macOS uses a different backend and does not suffer from this issue.
Constructs a new file system watcher object with the given
parent
.- __init__(paths[, parent=None])
- Parameters:
paths – list of strings
parent –
QObject
Constructs a new file system watcher object with the given
parent
which monitors the specifiedpaths
list.- addPath(file)¶
- Parameters:
file – str
- Return type:
bool
Adds
path
to the file system watcher ifpath
exists. The path is not added if it does not exist, or if it is already being monitored by the file system watcher.If
path
specifies a directory, thedirectoryChanged()
signal will be emitted whenpath
is modified or removed from disk; otherwise thefileChanged()
signal is emitted whenpath
is modified, renamed or removed.If the watch was successful, true is returned.
Reasons for a watch failure are generally system-dependent, but may include the resource not existing, access failures, or the total watch count limit, if the platform has one.
Note
There may be a system dependent limit to the number of files and directories that can be monitored simultaneously. If this limit is been reached,
path
will not be monitored, and false is returned.See also
- addPaths(files)¶
- Parameters:
files – list of strings
- Return type:
list of strings
Adds each path in
paths
to the file system watcher. Paths are not added if they not exist, or if they are already being monitored by the file system watcher.If a path specifies a directory, the
directoryChanged()
signal will be emitted when the path is modified or removed from disk; otherwise thefileChanged()
signal is emitted when the path is modified, renamed, or removed.The return value is a list of paths that could not be watched.
Reasons for a watch failure are generally system-dependent, but may include the resource not existing, access failures, or the total watch count limit, if the platform has one.
Note
There may be a system dependent limit to the number of files and directories that can be monitored simultaneously. If this limit has been reached, the excess
paths
will not be monitored, and they will be added to the returnedQStringList
.See also
- directories()¶
- Return type:
list of strings
Returns a list of paths to directories that are being watched.
See also
- directoryChanged(path)¶
- Parameters:
path – str
This signal is emitted when the directory at a specified
path
is modified (e.g., when a file is added or deleted) or removed from disk. Note that if there are several changes during a short period of time, some of the changes might not emit this signal. However, the last change in the sequence of changes will always generate this signal.See also
- fileChanged(path)¶
- Parameters:
path – str
This signal is emitted when the file at the specified
path
is modified, renamed or removed from disk.Note
As a safety measure, many applications save an open file by writing a new file and then deleting the old one. In your slot function, you can check
watcher.files().contains(path)
. If it returnsfalse
, check whether the file still exists and then calladdPath()
to continue watching it.See also
- files()¶
- Return type:
list of strings
Returns a list of paths to files that are being watched.
See also
- removePath(file)¶
- Parameters:
file – str
- Return type:
bool
Removes the specified
path
from the file system watcher.If the watch is successfully removed, true is returned.
Reasons for watch removal failing are generally system-dependent, but may be due to the path having already been deleted, for example.
See also
- removePaths(files)¶
- Parameters:
files – list of strings
- Return type:
list of strings
Removes the specified
paths
from the file system watcher.The return value is a list of paths which were not able to be unwatched successfully.
Reasons for watch removal failing are generally system-dependent, but may be due to the path having already been deleted, for example.
See also