➜

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 palaviv
Recipients Arfrever, Dima.Tisnek, Jim.Jewett, Robin.Schreiber, berker.peksag, feuermurmel, ghaering, larry, palaviv, petri.lehtinen, pitrou, serhiy.storchaka, vstinner
Date 2017-03-01.17:44:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488390297.44.0.774819670504.issue9303@psf.upfronthosting.co.za>
In-reply-to
Content 
from https://www.sqlite.org/changes.html:
sqlite3_open_v2 - 2007-09-04 (3.5.0) alpha
sqlite3_prepare_v2 - 2007-01-04 (3.3.9)
sqlite3_close_v2 - 2012-09-03 (3.7.14)

In issue 29355 Ma Lin says that RHEL6 comes with SQLite 3.6.x. I think that removing that removing the check for sqlite3_prepare_v2 and sqlite3_open_v2 is fine but sqlite3_close_v2 need to stay.

> Don't forget about Windows where autotools are not used.

What should I do for this to work on windows?
History
Date User Action Args
2017-03-01 17:44:57palavivsetrecipients: + palaviv, ghaering, pitrou, vstinner, larry, Arfrever, feuermurmel, petri.lehtinen, berker.peksag, Dima.Tisnek, Jim.Jewett, serhiy.storchaka, Robin.Schreiber
2017-03-01 17:44:57palavivsetmessageid: <1488390297.44.0.774819670504.issue9303@psf.upfronthosting.co.za>
2017-03-01 17:44:57palavivlinkissue9303 messages
2017-03-01 17:44:57palavivcreate