[issue42241] Backport SQLite trace API v2

2020-11-02 Thread Dong-hee Na


Dong-hee Na  added the comment:

We often submit the backported patch by using the backport label from the 
origin PR.
(https://github.com/python/cpython/pull/19581)

So please discuss about the bacporting on bpo-40318

--
nosy: +corona10
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42241] Backport SQLite trace API v2

2020-11-02 Thread Erlend Egeberg Aasland


Change by Erlend Egeberg Aasland :


--
keywords: +patch
nosy: +erlendaasland
nosy_count: 1.0 -> 2.0
pull_requests: +22016
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/19581

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42241] Backport SQLite trace API v2

2020-11-01 Thread Samuel Marks


New submission from Samuel Marks :

Backports https://github.com/python/cpython/pull/19581 
https://bugs.python.org/issue40318 as per https://bugs.python.org/issue42229

--
components: Build
messages: 380185
nosy: samuelmarks
priority: normal
pull_requests: 22011
severity: normal
status: open
title: Backport SQLite trace API v2
type: compile error
versions: Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com