Martin v. Löwis <[EMAIL PROTECTED]> added the comment:
I agree with Amaury's analysis (except that the preferred way to
override it is to define SQLITE_THREADSAFE directly). If it's not
defined, it defaults to 1.
Closing as works-for-me.
--
resolution: -> works for me
status: open -> c
Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:
It seems that it is already the case. On Windows, a one-big-source-file
version of sqlite is used, fetched from
http://svn.python.org/projects/external/sqlite-3.5.9
(see Tools/buildbot/external-common.bat)
and in this file, SQLITE_THRE
New submission from Gerhard Häring <[EMAIL PROTECTED]>:
According to http://www.sqlite.org/faq.html#q6 SQLite should be built
with SQLITE_THREADSAFE defined when the library is used in a
multithreaded context.
This doesn't mean that the connection objects can then be shared between
threads. This
