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 ronaldoussoren
Recipients ned.deily, ronaldoussoren, vstinner
Date 2017-06-13.19:24:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1497381843.05.0.552159412365.issue30646@psf.upfronthosting.co.za>
In-reply-to
Content
See also <https://sqlite.org/c3ref/enable_shared_cache.html>. Apple basically disabled this function starting at macOS 10.7, that's why there's a warning.

It is possible to suppress the warning, but I don't think its worth the trouble.

BTW. The python documentation for this function claims this changes a thread-local setting, but the SQLite documentation says this is a process global setting in SQLite 3.5.0 and later (released in 2007).  It is possible to make behaviour match the python documentation by making _sqlite3.enable_shared_cache store a flag that's used in the call to sqlite3_open_v2. That would be a backward compatibility concern (there's bound to be users that rely on the current behavior), but would also avoid this warning.
History
Date User Action Args
2017-06-13 19:24:03ronaldoussorensetrecipients: + ronaldoussoren, vstinner, ned.deily
2017-06-13 19:24:03ronaldoussorensetmessageid: <1497381843.05.0.552159412365.issue30646@psf.upfronthosting.co.za>
2017-06-13 19:24:03ronaldoussorenlinkissue30646 messages
2017-06-13 19:24:03ronaldoussorencreate