This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients intchanter, ned.deily
Date 2017-01-10.20:25:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484079959.41.0.402270066151.issue29230@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the report.  From a quick look at the macOS crash report, I'm guessing you are running with the Apple-supplied system Python 2.7 but with a virtualenv.  In any case, the Apple-supplied libsqlite3 is in use and there are previously reported problems using it with multiple threads, possibly multiple processes, accessing the same database file; see for example Issue27126.  Suggest you try using a Python instance that is linked with its own version of a current libsqlite3, rather than with the system one: Pythons installed from current python.org macOS installers, from Macports, or (probably) Homebrew should all fit the bill and see if the problems go away.
History
Date User Action Args
2017-01-10 20:25:59ned.deilysetrecipients: + ned.deily, intchanter
2017-01-10 20:25:59ned.deilysetmessageid: <1484079959.41.0.402270066151.issue29230@psf.upfronthosting.co.za>
2017-01-10 20:25:59ned.deilylinkissue29230 messages
2017-01-10 20:25:59ned.deilycreate