Re: pysqlite design decisions

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Roger Binns wrote:
> [...]
> My current APSW already requires SQLite 3.3.8 and due to bugs I found in
> that (memory leaks), I expect you'd be best off with the next release of
> SQLite.  I assume Python is going to have to hold the SQLite version the
> same for the lifetime of 2.5 otherwise code will break between different
> versions.

Did you mean SQLite version or pysqlite version?

I certainly won't add any features to the sqlite3 module in Python 2.5.x.
It will be equivalent to the latest 2.3.x release of pysqlite.

As for which SQLite version is the recommended one, I got asked that
repeatedly on the python developer list, and couldn't really answer. It's
only relevant for the Python win32 installer anyway, and I would try to
update the SQLite DLL included to a more recent one for Python 2.5.1
(currently it's at version 3.3.4). You seem to be better informed in
low-level SQLite matters, would you recommend that I update the DLL?

- -- Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFde/ldIO4ozGCH14RAn5JAJ9NiCZuvhLhDeRREcPmBgfIK+hnugCgtlUW
EW0WsfGii5l/Y/0seucIYyE=
=KR01
-----END PGP SIGNATURE-----