From 2cbedbee452a63e4d10c9a47c3c0f1c89f8be7a6 Mon Sep 17 00:00:00 2001 From: Daniele Varrazzo Date: Sun, 4 Mar 2012 05:09:46 +0000 Subject: [PATCH] Dropped test about close() on closed connection raising an exception This seems unnecessary and has caused problems to a few. The DB-SIG seems agreeing on the change: http://mail.python.org/pipermail/db-sig/2011-October/005811.html --- tests/dbapi20.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tests/dbapi20.py b/tests/dbapi20.py index 59232a56..6231ed74 100644 --- a/tests/dbapi20.py +++ b/tests/dbapi20.py @@ -380,7 +380,9 @@ class DatabaseAPI20Test(unittest.TestCase): self.assertRaises(self.driver.Error,con.commit) # connection.close should raise an Error if called more than once - self.assertRaises(self.driver.Error,con.close) + # Issue discussed on DB-SIG: consensus seem that close() should not + # raised if called on closed objects. Issue reported back to Stuart. + # self.assertRaises(self.driver.Error,con.close) def test_execute(self): con = self._connect()