Larry Hastings added the comment:
I assumed that you guys took responsibility for the binary installers, and the
decision was up to you. But I'm happy to take ultimate responsibility for the
decision to ship SQLite 3.8.3 with 3.4 if that's what policy demands, and yes I
give it my blessing.
According to the release notes:
http://www.sqlite.org/draft/changes.html
there are two new constants: SQLITE_DETERMINISTIC and SQLITE_READONLY_DBMOVED.
It looks like there's no point in adding these int constants to the module, as
the latter is an error (and those never escape the module) and the former is a
flag to creating a "function" (and there's no exposed means to pass in flags
here).
Do we need to do anything to support additional features in 3.8.3, like this
SQLITE_DETERMINISTIC flag?
Roping in "ghaering", the sqlite expert from the list.
----------
nosy: +ghaering
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20465>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
