Re: Py 3.2: sqlite can't operate on a closed cursor

From	Gnarlodious <gnarlodious@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: Py 3.2: sqlite can't operate on a closed cursor
Date	2011-05-07 20:17 -0700
Organization	http://groups.google.com
Message-ID	<c372dcf5-a584-400b-9ced-d1fd55babbc6@l2g2000prg.googlegroups.com> (permalink)
References	<2ba90070-ee5e-4388-a713-c612a7419db0@s16g2000prf.googlegroups.com>

Show all headers | View raw

It turns out Python 3.2 now honors closing sqlite connections opened
in another module. Previous versions allowed you to have identically
named sqlite connections open in other modules. Python 3.2 apparently
treats them all as the same connection.

Hopefully some other victim will find this, because it wasn't written
in the documentation
http://docs.python.org/dev/whatsnew/3.2.html#sqlite3

-- Gnarlie

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Py 3.2: sqlite can't operate on a closed cursor Gnarlodious <gnarlodious@gmail.com> - 2011-05-07 19:55 -0700
  Re: Py 3.2: sqlite can't operate on a closed cursor Gnarlodious <gnarlodious@gmail.com> - 2011-05-07 20:17 -0700

csiph-web