From a676f6a0e081e54a0a57dbfca2d14fee381e7d92 Mon Sep 17 00:00:00 2001
From: Julian Andres Klode <jak@debian.org>
Date: Tue, 21 Jul 2009 16:55:11 +0200
Subject: python/lock.cc: Fix refcount in systemlock_enter and behavior of
 systemlock_exit.

---
 python/lock.cc | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

(limited to 'python/lock.cc')

diff --git a/python/lock.cc b/python/lock.cc
index aac2d25a..75665779 100644
--- a/python/lock.cc
+++ b/python/lock.cc
@@ -33,9 +33,18 @@ static PyObject *systemlock_exit(PyObject *self, PyObject *args)
                            &traceback)) {
         return 0;
     }
-    if ((! exc_type || exc_type == Py_None) && _system->UnLock() == 0) {
-        return HandleErrors();
+
+    if (_system->UnLock() == 0) {
+        // The unlock failed. If no exception happened within the suite, we
+        // will raise an error here. Otherwise, we just display the error, so
+        // Python can handle the original exception instead.
+        HandleErrors();
+        if (exc_type == Py_None)
+            return NULL;
+        else
+            PyErr_WriteUnraisable(self);
     }
+    // Return False, as required by the context manager protocol.
     Py_RETURN_FALSE;
 }
 
@@ -45,6 +54,7 @@ static PyObject *systemlock_enter(PyObject *self, PyObject *args)
         return NULL;
     if (!_system->Lock())
         return HandleErrors();
+    Py_INCREF(self);
     return self;
 }
 
-- 
cgit v1.2.3