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 fschulze
Recipients berker.peksag, fschulze, ghaering, jaraco, ned.deily, palaviv, r.david.murray, serhiy.storchaka, socketpair, xiang.zhang
Date 2016-11-25.12:17:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480076274.07.0.155198653114.issue28518@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, I reread https://docs.python.org/3/library/sqlite3.html#controlling-transactions several times now. I think it's confusing.

I want explicit transaction handling, but ``isolation_level = None`` turns on "autocommit mode". Unfortunately I don't have suggestions on how to improve the documentation.

For us, ``isolation_level = None`` and the explicit ``begin immediate`` seems to be the correct way and it works with all Python versions, including 3.6.0.

So, I would say this is "not a bug" in Python, but my understanding of the sqlite3 module is flawed. The documentation could be better, but I don't know how to make it better.
History
Date User Action Args
2016-11-25 12:17:54fschulzesetrecipients: + fschulze, ghaering, jaraco, ned.deily, r.david.murray, socketpair, berker.peksag, serhiy.storchaka, xiang.zhang, palaviv
2016-11-25 12:17:54fschulzesetmessageid: <1480076274.07.0.155198653114.issue28518@psf.upfronthosting.co.za>
2016-11-25 12:17:54fschulzelinkissue28518 messages
2016-11-25 12:17:53fschulzecreate