notmuch/bindings, branch 0.5

Merge in ruby bindings.

2010-11-08T18:08:34Z

Thanks to Ali Polatel for these bindings. This code was fetched from the ruby branch of: git://github.com/alip/notmuch.git

python: lambda(p) is not P3k-compliant

2010-10-28T19:12:10Z

Signed-off-by: Sebastian Spaeth

python: Import explicit including package name

2010-10-28T19:12:04Z

To make python3 happy Signed-off-by: Sebastian Spaeth

ruby: Don't barf if an object is destroyed more than once

2010-06-06T06:18:00Z

Raise RuntimeError instead. Also revise Notmuch::Database a bit. Add Notmuch::Database.open singleton method.

ruby: Use rb_scan_args()

2010-06-06T06:17:57Z

ruby: Kill garbage collection related cruft.

2010-06-06T06:17:47Z

Let the user destroy objects that she wants explicitly. It's not possible to specify the order objects are garbage collected. See id:86y6f8v838.fsf@harikalardiyari.ev on ruby-talk for more information.

ruby: First attempt at fixing gc for ruby-1.9

2010-06-06T06:17:30Z

ruby: fix documentation of DB.upgrade!

2010-06-06T06:17:06Z

Initial ruby bindings

2010-06-06T06:16:53Z

python: have docs reflect current return value behavior

2010-05-18T18:11:59Z

Database.find_message() used to be able to reliably indicate whether a message exists or not (in which case it returns None). However, the recent API change of the notmuch library means we will return None even for all Xapian exceptions, which happens e.g. when the current Database has been modified by another project. Therefore the return value of None cannot be reliably be used to indicate whether a message exists or not. Make the docs state that explicitely. Signed-off-by: Sebastian Spaeth