Backport SQLite trace API v2

[SamuelMarks]

BPO	42242
Nosy	@corona10, @erlend-aasland, @SamuelMarks
PRs	bpo-42242: Backport migration to SQLite3 trace v2 #23099 bpo-40318: Migrate to SQLite3 trace v2 API #19581

^{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 2020-11-02.08:14:31.655>
created_at = <Date 2020-11-02.07:26:01.043>
labels = ['build', '3.8']
title = 'Backport SQLite trace API v2'
updated_at = <Date 2020-11-02.09:55:54.901>
user = 'https://github.com/SamuelMarks'

bugs.python.org fields:

activity = <Date 2020-11-02.09:55:54.901>
actor = 'samuelmarks'
assignee = 'none'
closed = True
closed_date = <Date 2020-11-02.08:14:31.655>
closer = 'corona10'
components = ['Build']
creation = <Date 2020-11-02.07:26:01.043>
creator = 'samuelmarks'
dependencies = []
files = []
hgrepos = []
issue_num = 42242
keywords = ['patch']
message_count = 4.0
messages = ['380186', '380193', '380195', '380202']
nosy_count = 3.0
nosy_names = ['corona10', 'erlendaasland', 'samuelmarks']
pr_nums = ['23099', '19581']
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue42242'
versions = ['Python 3.8']

[SamuelMarks]

Backports #19581 https://bugs.python.org/issue40318 as per https://bugs.python.org/issue42229

See also 3.9 backporting: https://bugs.python.org/issue42241

[not sure if this is how you do backporting, a new issue and GH PR for each supported release tag?]

[erlend-aasland]

[not sure if this is how you do backporting, a new issue and GH PR for each supported release tag?]

Backports are almost always created as backports of a specific GitHub pull request. The pull request is labelled as, for example, "needs backport to 3.9", and a bot will automatically try to cherry-pick the squashed commit to the target branch. So, if we wanted to backport #63780, we would do that directly from the original pull request over at GitHub. That will also preserve commit meta-data.

See also:
https://devguide.python.org/committing/?highlight=backport#backporting-changes-to-an-older-version

[corona10]

We often submit the backported patch by using the backport label from the origin PR.
(#19581)

So please discuss the backporting on bpo-40318

[SamuelMarks]

Done, thanks for the how-to:

• [3.8] bpo-40318: Migrate to SQLite3 trace v2 API (GH-19581) #23103 [3.8]
• [3.9] bpo-40318: Migrate to SQLite3 trace v2 API (GH-19581) #23102 [3.9]