Module pyinotify :: Class _SysProcessEvent
[show private | hide private]
[frames | no frames]

Type _SysProcessEvent

   object --+    
            |    
_ProcessEvent --+
                |
               _SysProcessEvent


There is three kind of processing according to each event:
  1. special handling (deletion from internal container, bug, ...).
  2. default treatment: which is applied to most of events.
  1. IN_ISDIR is never sent alone, he is piggybacked with a standart event, he is not processed as the others events, instead, its value is captured and appropriately aggregated to dst event.

Method Summary
  __init__(self, wm)
  cleanup(self)
Cleanup (delete) old (>1mn) records contained in self._mv_cookie and self._mv.
  process_default(self, raw_event, to_append)
Common handling for the following events:
  process_IN_CREATE(self, raw_event)
If the event concerns a directory and the auto_add flag of the targetted watch is set to True, a new watch is added on this new directory, with the same attributes's values than those of this watch.
  process_IN_IGNORED(self, raw_event)
The watch descriptor raised by this event is now ignored (forever), it can be safely deleted from watch manager dictionary.
  process_IN_MOVE_SELF(self, raw_event)
FIXME: Pending BUG This method is bugged, this event is raised when the watched item was moved, so we must update its path, but under circumstances it can be impossible: if its parent directory and its destination directory aren't watched.
  process_IN_MOVED_FROM(self, raw_event)
Map the cookie with the source path (+ date for cleaning).
  process_IN_MOVED_TO(self, raw_event)
Map the source path with the destination path (+ date for cleaning).
  process_IN_Q_OVERFLOW(self, raw_event)
Only signal overflow, most of the common flags are irrelevant for this event (path, wd, name).
    Inherited from _ProcessEvent
  __call__(self, event)
To behave like a functor the object must be callable.
  __str__(self)
    Inherited from object
  __delattr__(...)
x.__delattr__('name') <==> del x.name
  __getattribute__(...)
x.__getattribute__('name') <==> x.name
  __hash__(x)
x.__hash__() <==> hash(x)
  __new__(T, S, ...)
T.__new__(S, ...) -> a new object with type S, a subtype of T
  __reduce__(...)
helper for pickle
  __reduce_ex__(...)
helper for pickle
  __repr__(x)
x.__repr__() <==> repr(x)
  __setattr__(...)
x.__setattr__('name', value) <==> x.name = value

Method Details

__init__(self, wm)
(Constructor)

Parameters:
wm - Watch Manager.
           (type=WatchManager instance)
Overrides:
__builtin__.object.__init__

cleanup(self)

Cleanup (delete) old (>1mn) records contained in self._mv_cookie and self._mv.

process_default(self, raw_event, to_append={})

Common handling for the following events:

IN_ACCESS, IN_MODIFY, IN_ATTRIB, IN_CLOSE_WRITE, IN_CLOSE_NOWRITE, IN_OPEN, IN_DELETE, IN_DELETE_SELF, IN_UNMOUNT.

process_IN_CREATE(self, raw_event)

If the event concerns a directory and the auto_add flag of the targetted watch is set to True, a new watch is added on this new directory, with the same attributes's values than those of this watch.

process_IN_IGNORED(self, raw_event)

The watch descriptor raised by this event is now ignored (forever), it can be safely deleted from watch manager dictionary. After this event we can be sure that neither the event queue neither the system will raise an event associated to this wd.

process_IN_MOVE_SELF(self, raw_event)

FIXME: Pending BUG This method is bugged, this event is raised when the watched item was moved, so we must update its path, but under circumstances it can be impossible: if its parent directory and its destination directory aren't watched. The kernel (see include/linux/fsnotify.h) doesn't bring us enough informations like the destination path of moved items.

process_IN_MOVED_FROM(self, raw_event)

Map the cookie with the source path (+ date for cleaning).

process_IN_MOVED_TO(self, raw_event)

Map the source path with the destination path (+ date for cleaning).

process_IN_Q_OVERFLOW(self, raw_event)

Only signal overflow, most of the common flags are irrelevant for this event (path, wd, name).

Generated by Epydoc 2.1 on Tue Jul 10 21:40:43 2007 http://epydoc.sf.net