notmuch/bindings/python, branch debian/0.11.1-1

version: bump to 0.11.1

2012-02-03T12:32:49Z

also semi-automatically update man page and python bindings versions.

python: fix error handling

2012-01-23T11:44:08Z

Before 3434d1940 the return values of libnotmuch functions were declared as c_void_p and the code checking for errors compared the returned value to None, which is the ctypes equivalent of a NULL pointer. But said commit wrapped all the data types in python classes and the semantic changed in a subtle way. If a function returns NULL, the wrapped python value is falsish, but no longer equal to None. Backported from master to 0.11.

Update version to 0.11

2012-01-13T23:58:36Z

version: update to 0.11~rc3

2012-01-09T11:05:40Z

We found another serious-ish bug during freeze.

version: bump to 0.11~rc2

2012-01-02T10:50:07Z

This to "celebrate" pushing a bugfix in at the last minute.

version: update version to 0.11~rc1

2011-12-26T03:09:17Z

and keep python, man page, and debian package in sync.

Merge branch 'release'

2011-12-06T23:39:33Z

Conflicts: NEWS Conflicts resolved by inserting the 0.10.2 stanza before 0.11

fix format string in Message.unicode

2011-12-06T20:56:40Z

Since 2b0116119160f2dc83, Message.__str__ doesn't construct a hash containing the thread data before constructing the formatstring. This changes the formatstring to accept positional parameters instead of a hash.

python: Remove stray debug comment

2011-12-06T12:36:48Z

This slipped in wrongly in commit 71e0082eff (due to my fault). Signed-off-by: Sebastian Spaeth

python: use wrapped notmuch_*_t types instead of raw pointers

2011-12-06T12:34:30Z

Now that types are checked correctly, we also need to make sure that all the arguments actually are instances of these types. Otherwise the function calls will fail and raise an exception similar to this one: ctypes.ArgumentError: argument 3: : expected LP_LP_NotmuchMessageS instance instead of pointer to c_void_p