[issue27190] Check sqlite3_version before allowing check_same_thread = False

2016-06-12 Thread Berker Peksag
Berker Peksag added the comment: Thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.5 ___ Python tracker

[issue27190] Check sqlite3_version before allowing check_same_thread = False

2016-06-12 Thread Roundup Robot
Roundup Robot added the comment: New changeset 12bf71b9f1cd by Berker Peksag in branch '3.5': Issue #27190: Raise NotSupportedError if sqlite3 is older than 3.3.1 https://hg.python.org/cpython/rev/12bf71b9f1cd New changeset 4502cff170c2 by Berker Peksag in branch 'default': Issue #27190: Merge

[issue27190] Check sqlite3_version before allowing check_same_thread = False

2016-06-03 Thread Dave Sawyer
Dave Sawyer added the comment: This can go into bugfix branches. In fact, it's most likely to be helpful there because they are more likely to be running with a version of sqlite 10 years old. I use the sqlite3_libversion_number() call because I'm testing against the version of sqlite

[issue27190] Check sqlite3_version before allowing check_same_thread = False

2016-06-02 Thread Berker Peksag
Changes by Berker Peksag : -- components: +Extension Modules ___ Python tracker ___

[issue27190] Check sqlite3_version before allowing check_same_thread = False

2016-06-02 Thread Berker Peksag
Berker Peksag added the comment: Thanks for the patch. I'm not sure we can apply the patch to bugfix branches. You can use SQLITE_VERSION_NUMBER to check sqlite3 version. -- nosy: +berker.peksag stage: -> patch review versions: +Python 3.6 ___

[issue27190] Check sqlite3_version before allowing check_same_thread = False

2016-06-02 Thread Dave Sawyer
New submission from Dave Sawyer: Starting in sqlite version 3.3.1 (Jan 2006) multiple threads can share the same connection. Python allows you do use this with the check_same_thread parameter of sqlite3.connect() method. It's almost certain users have a late enough version of sqlite that they