I fear it's too late for Python-3.6, but sqlite-3.15.1 fixes an old annoying bug (hidden since 3.8.0), and arriving tomorrow (nov.24th) sqlite-3.15.2 should be the well ".2" stabilized version of recent 3.15 improvements towards SQL standard (support for row values)

If there is no special bugs left in Python-3.6.0b4 and everybody is happy, I would suggest you upgrade from sqlite-3.14.2 to sqlite-3.15.2

too late for sqlite-0.15.2 in Python-3.6.0rc ?

Yes, we're not going to change library versions for the 3.6.0 installers at this point.  Upgrade for 3.7.0 is fine and possibly for a 3.6.x maintenance release if warranted.  I suggest holding off on any patches until we're closer to those releases as there may be subsequent SQLite updates.

I understand the decision. Yet it always baffles me that a version correcting known bugs is not included at beta stage.

I don't think we have anyone actively tracking SQLite right now, like we do for OpenSSL.

All it really needs is someone to prepare and test the patch during the beta period, and to be available in case more fixes are required. At this stage, we're in the RC period, so there really needs to be a recall-level issue to justify a change, and even then we'd prefer a maintenance update rather than a feature update (e.g. 3.14.3 vs. 3.15.x - if it's not a recall-level issue for SQLite, then it's hard to call it a recall-level issue for Python).

Is this something we want to include for the upcoming 3.6.1 release?
The latest sqlite version is 3.17.0.

python-3.7 should include the latest stable sqlite, at the time of last alpha.

Thanks, Big Stone. Setting the version to 3.7.

In an effort to not forget about this, I'm setting it to deferred blocker.

> In an effort to not forget about this, I'm setting it to deferred blocker.

Should we mark issue 30952 'deferred blocker' too?

Oh wow, I didn't even know that Python included a copy of SQLite for Windows and macOS installers! I added it to my list of "embedded libraries" :-)
http://haypo-notes.readthedocs.io/cpython.html#embedded-libraries

New changeset 31af650ee25f65794b75d4dfefed6fe4758781c1 by Mariatta in branch 'master':
bpo-28791: Update Windows builds to use SQLite 3.21.0. (GH-4246)
https://github.com/python/cpython/commit/31af650ee25f65794b75d4dfefed6fe4758781c1

> sqlite-3.15.1 fixes an old annoying bug (hidden since 3.8.0)

Since the bug seems to be important, maybe it's worth it to backport the commit upgrading SQLite to Python 2.7 and 3.6?

I'd say that's up to Ned and Benjamin.  It's a very simple backport at this point.

+1 for backporting.

New changeset ca7562a7fea61646c1b40ace04deecf9903d34a1 by Ned Deily (Mariatta) in branch 'master':
bpo-28791: Update macOS installer to use SQLite 3.21.0. (#4245)
https://github.com/python/cpython/commit/ca7562a7fea61646c1b40ace04deecf9903d34a1

New changeset a72e7bf563d5a9fb706a1775f5ae883a91b8a99f by Ned Deily in branch '3.6':
[3.6] bpo-28791: Update macOS installer to use SQLite 3.21.0. (#4245) (#4711)
https://github.com/python/cpython/commit/a72e7bf563d5a9fb706a1775f5ae883a91b8a99f

I've updated the macOS installer for 3.7.0 and for 3.6.4.  I'll leave this open for possible updating the Windows installer for 3.6.x (OK by me) and for possible updates for 2.7.x.

> Should we mark issue 30952 'deferred blocker' too?

No, that's a different matter.  AFAICT, there is no standard option for that.

Tried to get miss-islington to backport Windows installer change to 3.6, did not work.

I'll work on the backport PR.

New changeset e2ba5523192a9cff125fce2ce530bec574353f7b by Mariatta in branch '3.6':
bpo-28791: Update Windows builds to use SQLite 3.21.0. (GH-4246). (GH-4717)
https://github.com/python/cpython/commit/e2ba5523192a9cff125fce2ce530bec574353f7b

Backport to 3.6 is done. But I personally won't be bothering with 2.7 :)

Looks like unless Benjamin would like 2.7.x updated, this can now be closed.

Since we have a more recent "update SQLite" issue in bpo-35360, I'm going to go ahead and close this one.