➜

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 malin
Recipients berker.peksag, malin, palaviv
Date 2017-01-24.04:38:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485232693.83.0.291296040478.issue29355@psf.upfronthosting.co.za>
In-reply-to
Content 
In CPython 3.6.0, sqlite3 module uses sqlite3_stmt_readonly(), however this function is only available on SQLite 3.7.4+ (release on 2010-12-07).
Then CPython 3.6.0 can not be compiled on RHEL6 (with SQLite 3.6.x), complaints: issue29098, issue29325.

sqlite3_stmt_readonly() was introduced in 284676cf2ac8, it was used twice [1][2], but it seems that we can avoid using this function in both of them.

[1] https://hg.python.org/cpython/file/3.6/Modules/_sqlite/cursor.c#l517
With palaviv's patches of issue28518, we can eliminate sqlite3_stmt_readonly() in here.

[2] https://hg.python.org/cpython/file/3.6/Modules/_sqlite/cursor.c#l612
We can use the old way in here, the old way is even better IMO.

This issue depends on issue28518.
History
Date User Action Args
2017-01-24 04:38:13malinsetrecipients: + malin, berker.peksag, palaviv
2017-01-24 04:38:13malinsetmessageid: <1485232693.83.0.291296040478.issue29355@psf.upfronthosting.co.za>
2017-01-24 04:38:13malinlinkissue29355 messages
2017-01-24 04:38:12malincreate