pysqlite: Evaluate removal of sqlite3_stmt_readonly

[phantal]

BPO	29325
Nosy	@bitdancer, @berkerpeksag, @animalize, @zhangyangyu, @palaviv

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2017-01-20.03:42:24.642>
created_at = <Date 2017-01-19.16:30:50.482>
labels = ['extension-modules', 'type-feature']
title = 'pysqlite: Evaluate removal of sqlite3_stmt_readonly'
updated_at = <Date 2017-01-23.13:38:28.850>
user = 'https://bugs.python.org/phantal'

bugs.python.org fields:

activity = <Date 2017-01-23.13:38:28.850>
actor = 'malin'
assignee = 'none'
closed = True
closed_date = <Date 2017-01-20.03:42:24.642>
closer = 'xiang.zhang'
components = ['Extension Modules']
creation = <Date 2017-01-19.16:30:50.482>
creator = 'phantal'
dependencies = []
files = []
hgrepos = []
issue_num = 29325
keywords = []
message_count = 7.0
messages = ['285804', '285872', '285874', '285875', '285876', '285907', '286086']
nosy_count = 6.0
nosy_names = ['r.david.murray', 'berker.peksag', 'malin', 'xiang.zhang', 'palaviv', 'phantal']
pr_nums = []
priority = 'normal'
resolution = 'third party'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue29325'
versions = []

[phantal]

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.

[zhangyangyu]

pysqlite is not part of Python stdlib so here is not the right place. :-(
Maybe you could go to https://github.com/ghaering/pysqlite for help.

[animalize]

sqlite3 module in CPython 3.6.0 also uses sqlite3_stmt_readonly(). see 284676cf2ac8.
sqlite3_stmt_readonly() 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
In palaviv's patch of bpo-28518, we can eliminate sqlite3_stmt_readonly() in here.

[2] https://hg.python.org/cpython/file/3.6/Modules/_sqlite/cursor.c#l612
We can using the old way, so that we can get around it in here.

[zhangyangyu]

Hi Ma Lin. If you find this is also a problem in sqlite3 module, feel free to open another issue against sqlite3. :-)

[animalize]

RHEL6's life-cycle is around 10 years [1], it will be alive until 2020.
https://access.redhat.com/support/policy/updates/errata/

Let's wait bpo-28518, IMO, that issue will decide whether we can get around sqlite3_stmt_readonly().

[bitdancer]

Python ships with RH6, and includes a working sqlite3 module. So if you are restricting yourself to software directly supported by RH6, you are fine. If you are installing python3.6 on your rh6 box, then you can also install a more up to date sqlite in order to get it to compile the sqlite3 module. So I don't see any actionable issue because of RH6 here, either for us or for pysqlite. The other issue is a different story, of course.

[animalize]

Just remind, there is a chance to remove sqlite3_stmt_readonly(). :)