-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.6 support: sqlite3.OperationalError: Safety level may not be changed inside a transaction #58
Comments
otherwise python 3.6 fails with sqlite3.OperationalError: Safety level may not be changed inside a transaction (fixes issue piskvorky#58)
How can this be reproduced? It doesn't come up in Travis Python 3.6 tests |
creating a new instance with autocommit=False triggers this here:
|
Looks like travis still does not fail. |
Let's check sqlite version used in Travis in #62 |
Hmm the sqlite version in travis is really old. |
Also fails with Ubuntu 17.04 (sqlite 3.15.2). |
Also fails in Ubuntu 16.10 (sqlite 3.14.1 / Python 3.6) |
otherwise python 3.6 fails with sqlite3.OperationalError: Safety level may not be changed inside a transaction (fixes issue piskvorky#58)
fails in python3.6 with
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File ".../site-packages/sqlitedict.py", line 371, in run
cursor.execute('PRAGMA synchronous=OFF')
sqlite3.OperationalError: Safety level may not be changed inside a transaction
The text was updated successfully, but these errors were encountered: