[docs] sqlite3 open parameter "check_same_thread" not documented (issue 27113)

[thomas at kluyver.me.uk]

http://bugs.python.org/review/27113/diff/17342/Doc/library/sqlite3.rst
File Doc/library/sqlite3.rst (right):

http://bugs.python.org/review/27113/diff/17342/Doc/library/sqlite3.rst#newcode194
Doc/library/sqlite3.rst:194: a connection from multiple threads. Be sure
to use SQLite version 3.3.1 or later
This version was released over a decade ago
(https://www.sqlite.org/chronology.html) - is it necessary to mention
the requirement? And if it is, can we include an indication that you
almost certainly have a new enough version, so people don't need to work
out how to find their sqlite version.

http://bugs.python.org/review/27113/diff/17342/Doc/library/sqlite3.rst#newcode195
Doc/library/sqlite3.rst:195: and use locking when writing to the
connection to avoid corruption.
According to the sqlite docs (http://www.sqlite.org/threadsafe.html),
the default mode is 'serialized', which does the necessary locking for
threads to share a connection. Unless Python is overriding this to use
one of the less protected modes, it shouldn't be necessary to use extra
locks around it.

http://bugs.python.org/review/27113/