Pyinotify

* Added support for new command line option `--comand` to run a shell command on each event.
* Notable bugfixes [[IN_Q_OVERFLOW handling|https://github.com/seb-m/pyinotify/commit/43f47fed3a28b7cd62cfcf1bcfa948d7499a0407]] and [[logger support|https://github.com/seb-m/pyinotify/commit/6bee47701efa5613605988af10593a3c69682ba3]].

* Added support for systems without ctypes / libc / libc+inotiy. This works by compiling a C file accessing inotify's syscalls (like in pyinotify 0.7.1). However it should be noted, this file is not compiled unless necessary, `setup.py` try to detect if it needs it or not. As before, in the most common case where `ctypes` are used to access inotify, `pyinotify.py` still can be used as a standalone file. For more details see [[this commit|https://github.com/seb-m/pyinotify/commit/fec920a2146f78802f1a28a7f4c47f5c97426a7e]]. Notice, currently inotify's system wide variables `max_user_instances` , `max_user_watches`, `max_queued_events` can only be accessed when ctypes are used otherwise there are set to `None`.
* Replaced exception `UnsupportedLibcVersionError` by `InotifyBindingNotFoundError`. `WatchManager.__init__()` may raise this exception on error.
* Improved the mitigation of [[this issue|https://github.com/seb-m/pyinotify/issues/2]].

* Added new command line options `--version`, `--raw-format` (to disable colorized output).
* Added new method `WatchManager.close()` to explicitly close inotify's file descriptor (and delete all watches), see [[commit|http://github.com/seb-m/pyinotify/commit/80e1afc95893350e6e59230993e26376e279327c]].
* Removed optional argument `force_kill` for notifier's daemonization, it could be abused, also support new argument `pid_file=False` to not write the pid into a file, see [[commit1|http://github.com/seb-m/pyinotify/commit/155e2f5d0dfeff210198856b2b03d53d8e810c52]] and [[commit2|http://github.com/seb-m/pyinotify/commit/909f985842fcae8a45d9591017112186e68a723d]].

* It is possible to stop `Notifier` instance from its associated event loop's callback function, see [[this commit|http://github.com/seb-m/pyinotify/commit/a3fbdda201166260886f2644f4fe725e5a832fd5]].
* It is safe now to call `add_watch()` multiple times on the same path without any risk of modifying existing watches, see [[this commit|http://github.com/seb-m/pyinotify/commit/f7510650b8e9950247d14841967eb64d0b2d0294]].
* Similar events can be coalesced together, see [[this commit|http://github.com/seb-m/pyinotify/commit/134f1628ed438995b0367c76ea749d9d11067eb6]].

* The syntax of exclusion filter files has changed see the [[related commit|http://github.com/seb-m/pyinotify/commit/7bbd6dab1c317314161567a6088076282100f736]] and the new syntax [[exclude.lst|http://github.com/seb-m/pyinotify/tree/master/python2/examples/exclude.lst]]. This new way of parsing external patterns is safer.
* Pyinotify is not licensed anymore under GPL2+, its new license is now the [[MIT License|http://www.opensource.org/licenses/mit-license.php]].
* This is the first release to support Python 3.

A new function was added in order to provide a minimal compatibility mode with Pyinotify 0.7.1. Call this function from your code only if it was developed for the old versions of Pyinotify (<= 0.7.1) (although you should strongly consider upgrading your code, read [[this link|http://github.com/seb-m/pyinotify/blob/master/NEWS_old]] for more details on what has changed). The compatibility mode is set to `False` by default therefore you have to make an explicit call to activate it (note that once this mode is activated at runtime, it is not possible to disable it).

python
import pyinotify
[... old code ...]
if __name__ == '__main__':
pyinotify.compatibily_mode() Turns on compatibility mode
[... old code ...]