diff options
| author | Daniele Varrazzo <daniele.varrazzo@gmail.com> | 2012-03-04 05:09:46 +0000 |
|---|---|---|
| committer | Daniele Varrazzo <daniele.varrazzo@gmail.com> | 2012-03-04 05:10:06 +0000 |
| commit | 2cbedbee452a63e4d10c9a47c3c0f1c89f8be7a6 (patch) | |
| tree | 9dbe6f8daca2fbc488e13fd15bf52baaec7ff07a /tests/dbapi20.py | |
| parent | 4eea8bc912096654bc65a5908b0d861f1e9bba32 (diff) | |
| download | psycopg2-2cbedbee452a63e4d10c9a47c3c0f1c89f8be7a6.tar.gz | |
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
Diffstat (limited to 'tests/dbapi20.py')
| -rw-r--r-- | tests/dbapi20.py | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/tests/dbapi20.py b/tests/dbapi20.py index 59232a5..6231ed7 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() |