module: | watchdog.events |
---|---|
synopsis: | File system events and event handlers. |
author: | yesudeep@google.com (Yesudeep Mangalapilly) |
Bases: object
Immutable type that represents a file system event that is triggered when a change occurs on the monitored file system.
All FileSystemEvent objects are required to be immutable and hence can be used as keys in dictionaries or be added to sets.
Bases: watchdog.events.FileSystemEvent
File system event representing any kind of file system movement.
Bases: watchdog.events.FileSystemMovedEvent
File system event representing file movement on the file system.
Bases: watchdog.events.FileSystemMovedEvent
File system event representing directory movement on the file system.
Generates moved events for file sytem objects within the moved directory.
Parameters: | _walker – Walker used to walk directory trees os.walk() style. Sanity tests use this parameter to inject a mock walker that behaves like os.walk(). |
---|---|
Returns: | iterable of event objects of type FileMovedEvent and DirMovedEvent. |
Bases: watchdog.events.FileSystemEvent
File system event representing file modification on the file system.
Bases: watchdog.events.FileSystemEvent
File system event representing directory modification on the file system.
Bases: watchdog.events.FileSystemEvent
File system event representing file creation on the file system.
Bases: watchdog.events.FileSystemEvent
File system event representing directory creation on the file system.
Bases: watchdog.events.FileSystemEvent
File system event representing file deletion on the file system.
Bases: watchdog.events.FileSystemEvent
File system event representing directory deletion on the file system.
Bases: object
Base file system event handler that you can override methods from.
Dispatches events to the appropriate methods.
Parameters: | event (FileSystemEvent) – The event object representing the file system event. |
---|
Catch-all event handler.
Parameters: | event (FileSystemEvent) – The event object representing the file system event. |
---|
Called when a file or directory is created.
Parameters: | event (DirCreatedEvent or FileCreatedEvent) – Event representing file/directory creation. |
---|
Called when a file or directory is deleted.
Parameters: | event (DirDeletedEvent or FileDeletedEvent) – Event representing file/directory deletion. |
---|
Called when a file or directory is modified.
Parameters: | event (DirModifiedEvent or FileModifiedEvent) – Event representing file/directory modification. |
---|
Called when a file or a directory is moved or renamed.
Parameters: | event (DirMovedEvent or FileMovedEvent) – Event representing file/directory movement. |
---|
Bases: watchdog.events.FileSystemEventHandler
Matches given patterns with file paths associated with occurring events.
(Read-only) True if path names should be matched sensitive to case; False otherwise.
Dispatches events to the appropriate methods.
Parameters: | event (FileSystemEvent) – The event object representing the file system event. |
---|
Bases: watchdog.events.FileSystemEventHandler
Matches given regexes with file paths associated with occurring events.
(Read-only) True if path names should be matched sensitive to case; False otherwise.
Dispatches events to the appropriate methods.
Parameters: | event (FileSystemEvent) – The event object representing the file system event. |
---|
Bases: watchdog.events.FileSystemEventHandler
Logs all the events captured.
module: | watchdog.observers.api |
---|---|
synopsis: | Classes useful to observer implementers. |
author: | yesudeep@google.com (Yesudeep Mangalapilly) |
Bases: watchdog.utils.bricks.OrderedSetQueue
Thread-safe event queue based on a thread-safe ordered-set queue to ensure duplicate FileSystemEvent objects are prevented from adding themselves to the queue to avoid dispatching multiple event handling calls when multiple identical events are produced quicker than an observer can consume them.
Bases: watchdog.utils.DaemonThread
Producer daemon thread base class subclassed by event emitters that generate events and populate a queue with them.
Parameters: |
|
---|
Override this method for cleaning up immediately before the daemon thread stops completely.
Queues a single event.
Parameters: | event (An instance of watchdog.events.FileSystemEvent or a subclass.) – Event to be queued. |
---|
Bases: watchdog.utils.DaemonThread
Consumer daemon thread base class subclassed by event observer threads that dispatch events from an event queue to appropriate event handlers.
Parameters: | timeout (float) – Event queue blocking timeout (in seconds). |
---|
Override this method to consume events from an event queue, blocking on the queue for the specified timeout before raising queue.Empty.
Parameters: |
|
---|---|
Raises : | queue.Empty |
The event queue which is populated with file system events by emitters and from which events are dispatched by a dispatcher thread.
Bases: watchdog.observers.api.EventDispatcher
Base observer.
Adds a handler for the given watch.
Parameters: |
|
---|
Removes a handler for the given watch.
Parameters: |
|
---|
Schedules watching a path and calls appropriate methods specified in the given event handler in response to file system events.
Parameters: |
|
---|---|
Returns: | An ObservedWatch object instance representing a watch. |
Unschedules a watch.
Parameters: | watch (An instance of ObservedWatch or a subclass of ObservedWatch) – The watch to unschedule. |
---|
module: | watchdog.observers |
---|---|
synopsis: | Observer that picks a native implementation if available. |
author: | yesudeep@google.com (Yesudeep Mangalapilly) |
Bases: watchdog.observers.polling.PollingObserver
Observer thread that schedules watching directories and dispatches calls to event handlers.
Adds a handler for the given watch.
Parameters: |
|
---|
The event queue which is populated with file system events by emitters and from which events are dispatched by a dispatcher thread.
Override this method instead of stop(). stop() calls this method.
Note that this method is called immediately after the daemon thread is signaled to halt.
Removes a handler for the given watch.
Parameters: |
|
---|
Schedules watching a path and calls appropriate methods specified in the given event handler in response to file system events.
Parameters: |
|
---|---|
Returns: | An ObservedWatch object instance representing a watch. |
Determines whether the daemon thread should continue running.
Determines whether the daemon thread should stop.
Signals the daemon thread to stop.
Event queue block timeout.
Unschedules a watch.
Parameters: | watch (An instance of ObservedWatch or a subclass of ObservedWatch) – The watch to unschedule. |
---|
Unschedules all watches and detaches all associated event handlers.
module: | watchdog.utils |
---|---|
synopsis: | Utility classes and functions. |
author: | yesudeep@google.com (Yesudeep Mangalapilly) |
hasattr() swallows exceptions. has_attribute() tests a Python object for the presence of an attribute.
Parameters: |
|
---|
Loads and returns a class definition provided a dotted path specification the last part of the dotted path is the class name and there is at least one module name preceding the class name.
Notes: You will need to ensure that the module you are trying to load exists in the Python path.
Examples: - module.name.ClassName # Provided module.name is in the Python path. - module.ClassName # Provided module is in the Python path.
What won’t work: - ClassName - modle.name.ClassName # Typo in module name. - module.name.ClasNam # Typo in classname.
Bases: threading.Thread
Daemon thread convenience class, sets a few properties and makes writing daemon threads a little easier.
module: | watchdog.utils.dirsnapshot |
---|---|
synopsis: | Directory snapshots and comparison. |
author: | yesudeep@google.com (Yesudeep Mangalapilly) |
Where are the moved events? They “disappeared”
This implementation does not take partition boundaries into consideration. It will only work when the directory tree is entirely on the same file system. More specifically, any part of the code that depends on inode numbers can break if partition boundaries are crossed. In these cases, the snapshot diff will represent file/directory movement as created and deleted events.
Windows does not have any concept of inodes, which prevents this snapshotter from determining file or directory renames/movement on it. The snapshotter does not try to handle this on Windows. File or directory movement will show up as creation and deletion events.
Please do not use this on a virtual file system mapped to a network share.
Bases: object
A snapshot of stat information of files in a directory.
Parameters: |
|
---|
Determines the path that an inode represents in a snapshot.
Parameters: | inode – inode number. |
---|
Returns a stat information object for the specified path from the snapshot.
Parameters: | path – The path for which stat information should be obtained from a snapshot. |
---|
Bases: object
Compares two directory snapshots and creates an object that represents the difference between the two snapshots.
Parameters: |
|
---|