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 erlendaasland
Recipients JelleZijlstra, erlendaasland
Date 2022-03-09.11:14:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ah, one of my very first contributions, bpo-40318, comes back to haunt me:

In bpo-40318, we migrated from the old SQLite trace API (sqlite3_trace) to SQLite trace v2 API (sqlite3_trace_v2). GH-19581, which introduced this change, introduced a bug: the old trace API _implicitly_ expanded bound parameters; the new trace API does not. However, there was no tests for this behaviour, so the regression was unnoticed[^1].

So, this bpo is actually a bug fix; not a feature. It should be backported to 3.10, which contains the regression.

I'm preparing a fix for GH-28240, and I'll prepare a 3.10 backport including both GH-2840 and its upcoming fix.

[^1]: There has been no bug reports regarding this change in behaviour, so it seems to have gone under most people's radar.
Date User Action Args
2022-03-09 11:14:46erlendaaslandsetrecipients: + erlendaasland, JelleZijlstra
2022-03-09 11:14:46erlendaaslandsetmessageid: <>
2022-03-09 11:14:46erlendaaslandlinkissue45138 messages
2022-03-09 11:14:46erlendaaslandcreate