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 berker.peksag, erlendaasland, lemburg, malin, serhiy.storchaka
Date 2021-12-06.10:38:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I mean, after this change, different versions of SQLite will behave differently.

Yes, this is explained in the news item:

    Fetch across rollback no longer raises :exc:`~sqlite3.InterfaceError`.
    Instead we leave it to the SQLite library to handle these cases.

> And give a message for SQLITE_ABORT_ROLLBACK to explain this problem.

I'm not sure this is a good idea; I believe letting the underlying SQLite library explain the error is better than trying to deduce stuff based on what was known at compile time and what we know at runtime.

> It just leaks resource, apart from this, there seems to be no problem.

Can you provide a reproducer? We've run this change through the ref. leak bots, and they are all green, so if there's a ref. leak, the test suite needs improvements.
Date User Action Args
2021-12-06 10:38:14erlendaaslandsetrecipients: + erlendaasland, lemburg, berker.peksag, serhiy.storchaka, malin
2021-12-06 10:38:14erlendaaslandsetmessageid: <>
2021-12-06 10:38:14erlendaaslandlinkissue44092 messages
2021-12-06 10:38:14erlendaaslandcreate