Berker Peksag added the comment:
Issue 27113 has a patch and more detailed description so I'm going to close
this one as a 'duplicate'.
Thanks for the report!
--
nosy: +berker.peksag
resolution: -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder: ->
Mark Lawrence added the comment:
@Daniel could you provide a patch for this?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16509
___
Thomas Kluyver added the comment:
The module docs do mention Older SQLite versions had issues with sharing
connections between threads. Presumably that means that sharing the connection
between threads is safe so long as you're not using 'older versions', but it
would be nice to have some
Thomas Kluyver added the comment:
This page also looks relevant: sqlite can be compiled or used in three
different threading modes. Presumably Python compiles/initialises it in the
serialised mode, which makes it safe to use a connection from different threads.
Changes by Thomas Kluyver tak...@gmail.com:
--
nosy: +takluyver
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16509
___
___
Python-bugs-list
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16509
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ghaering
stage: - needs patch
versions: +Python 3.2, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16509
___
New submission from Daniel Micay:
The sqlite3 documentation now includes a Multithreading section explaining
issues with older sqlite versions, but still doesn't directly cover disabling
check_same_thread beyond listing it as a possible parameter.
As far as I can tell, reusing sqlite
