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 phantal
Recipients phantal
Date 2017-01-19.16:30:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484843450.51.0.0079411502064.issue29325@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure where to request changes to pysqlite, so my apologies if this isn't the right place.

To begin with: I'll either end up building a newer version of sqlite myself or just accepting that pysqlite won't be part of this python installation.  However, I thought it might be useful to know that use of the function "sqlite3_stmt_readonly" is the only thing tying pysqlite to the current minimum requirement to use sqlite 3.7.4.

The currently available 'supported' version of sqlite for RHEL6 is 3.6.x and there's likely others out there who (for whatever reason) are stuck on an older release of sqlite and moving to the latest & greatest OS isn't [currently] feasible.
History
Date User Action Args
2017-01-19 16:30:50phantalsetrecipients: + phantal
2017-01-19 16:30:50phantalsetmessageid: <1484843450.51.0.0079411502064.issue29325@psf.upfronthosting.co.za>
2017-01-19 16:30:50phantallinkissue29325 messages
2017-01-19 16:30:50phantalcreate