From 8015cbff263606f009b5750d23b28ee332c25db8 Mon Sep 17 00:00:00 2001
From: Justus Winter <4winter@informatik.uni-hamburg.de>
Date: Sun, 22 Jan 2012 06:14:57 +0100
Subject: python: fix error handling

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.
---
 bindings/python/notmuch/tag.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'bindings/python/notmuch/tag.py')

diff --git a/bindings/python/notmuch/tag.py b/bindings/python/notmuch/tag.py
index ceb7244..71d81dd 100644
--- a/bindings/python/notmuch/tag.py
+++ b/bindings/python/notmuch/tag.py
@@ -70,7 +70,7 @@ class Tags(Python3StringMixIn):
         :TODO: Make the iterator optionally work more than once by
                cache the tags in the Python object(?)
         """
-        if tags_p is None:
+        if not tags_p:
             raise NotmuchError(STATUS.NULL_POINTER)
 
         self._tags = tags_p
-- 
cgit v1.2.3