-d fails to initiate daemon mode on Ubuntu Karmic

I found this in ~/.bzr_hookless_email.tracebook:

Traceback (most recent call last):
  File "/home/Checkouts/Bazaar/BazaarHooklessEmail/bzr_hookless_email.py", line 393, in <module>
    main()
  File "/home/Checkouts/Bazaar/BazaarHooklessEmail/bzr_hookless_email.py", line 105, in main
    mask = EventsCodes.IN_CREATE | EventsCodes.IN_MODIFY | EventsCodes.IN_MOVED_TO
AttributeError: type object 'EventsCodes' has no attribute 'IN_CREATE'

So I looked in bzr_hookless_email.py and it is assumed that the OP_FLAGS can all be accesed directly. The source code of pyinotify.py seems to indicate that this should work. However:

|> python -c "import pyinotify ; print pyinotify.EventsCodes.IN_MODIFY"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: type object 'EventsCodes' has no attribute 'IN_MODIFY'

So it seems that this way of accessing things is not longer working in Karmic whereas it worked fine in Jaunty.

The PyInotify documentation specifically says that pyinotify.IN_MODIFY should be used for all usage of PyInotify version 0.8 and greater, that pyinotify.EventsCodes.IN_MODIFY should not be used except where compatibiklity with PyInotify 0.7 is required.

I guess the question is whether to go with the new or retain compatibility with the old.

OK, this now works for me. I have pushed a branch to Launchpad lp:~russel/bzr-hookless-emai/russel-working.