Building with macoS system SQLite3 generates sqlite3_enable_shared_cache deprecation warning

[devnexen]

BPO	38311
Nosy	@ronaldoussoren, @ned-deily, @devnexen
PRs	bpo-38311: Avoid sqlite3_enable_shared_cache deprecation warning when building with the macOS system SQLite3 #16469
Superseder	bpo-24464: "sqlite3_enable_shared_cache" deprecation warning when compiling with macOS system SQLite3

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2019-09-29.06:35:27.358>
created_at = <Date 2019-09-28.21:17:09.860>
labels = ['OS-mac', 'build', '3.9']
title = 'Building with macoS system SQLite3 generates sqlite3_enable_shared_cache deprecation warning'
updated_at = <Date 2019-09-29.06:35:27.355>
user = 'https://github.com/devnexen'

bugs.python.org fields:

activity = <Date 2019-09-29.06:35:27.355>
actor = 'ned.deily'
assignee = 'none'
closed = True
closed_date = <Date 2019-09-29.06:35:27.358>
closer = 'ned.deily'
components = ['Build', 'macOS']
creation = <Date 2019-09-28.21:17:09.860>
creator = 'devnexen'
dependencies = []
files = []
hgrepos = []
issue_num = 38311
keywords = []
message_count = 2.0
messages = ['353485', '353486']
nosy_count = 3.0
nosy_names = ['ronaldoussoren', 'ned.deily', 'devnexen']
pr_nums = ['16469']
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '24464'
type = 'compile error'
url = 'https://bugs.python.org/issue38311'
versions = ['Python 3.9']

[ned-deily]

Thanks for the PR! As noted in my review comment of it, I believe a more robust approach would be needed to ensure that builds still work properly when building with a local copy of SQLite on macOS (not the system-supplied one), a common occurrence.

[ned-deily]

Sorry, I should have checked: this issue has come up at least a couple of times before, for example, bpo-30646 and bpo-24464 (still open with a slightly more compex patch). Let's just close this issue as a duplicate of the earlier one and continue any new discussion there.