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 serhiy.storchaka
Recipients Arfrever, Dima.Tisnek, Jim.Jewett, Robin.Schreiber, berker.peksag, feuermurmel, ghaering, larry, palaviv, petri.lehtinen, pitrou, serhiy.storchaka, vstinner
Date 2017-03-01.18:33:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <4258960.AQG26qZ8nk@raxxla>
In-reply-to <1488390297.44.0.774819670504.issue9303@psf.upfronthosting.co.za>
Content
> 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)

There are compile-time checks for supporting SQLite older than 3.2.2.

I think it is better to use the preprocessor rather of autotools for 
conformance with the rest of code.

> What should I do for this to work on windows?

On Windows manually written PC/pyconfig.h is used rather of generated by 
configure pyconfig.h. If you change pyconfig.h, you should update PC/pyconfig.h 
too. But I think this is not needed in this case. Just use 
SQLITE_VERSION_NUMBER.
History
Date User Action Args
2017-03-01 18:33:55serhiy.storchakasetrecipients: + serhiy.storchaka, ghaering, pitrou, vstinner, larry, Arfrever, feuermurmel, petri.lehtinen, berker.peksag, Dima.Tisnek, Jim.Jewett, Robin.Schreiber, palaviv
2017-03-01 18:33:55serhiy.storchakalinkissue9303 messages
2017-03-01 18:33:54serhiy.storchakacreate