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, serhiy.storchaka
Date 2021-05-19.10:42:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I've crafted a number of rollback tests, but it occurred to me that they are simply just testing SQLite behaviour; not sqlite3 behaviour. I had to adjust the tests according to which version of SQLite was used (for example introduced new behaviour). Such tests are bound to break as SQLite evolves. I'm not sure we want such tests in our test suite; it can make the CI fail for completely unrelated PRs. Suggesting to leave detailed rollback testing to SQLite and just keep a couple of basic tests in our suite.
Date User Action Args
2021-05-19 10:42:54erlendaaslandsetrecipients: + erlendaasland, lemburg, berker.peksag, serhiy.storchaka
2021-05-19 10:42:54erlendaaslandsetmessageid: <>
2021-05-19 10:42:54erlendaaslandlinkissue44092 messages
2021-05-19 10:42:54erlendaaslandcreate