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 malin, phantal, xiang.zhang
Date 2017-01-20.04:35:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484886955.83.0.853848539322.issue29325@psf.upfronthosting.co.za>
In-reply-to
Content
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 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 using the old way, so that we can get around it in here.
History
Date User Action Args
2017-01-20 04:35:55malinsetrecipients: + malin, xiang.zhang, phantal
2017-01-20 04:35:55malinsetmessageid: <1484886955.83.0.853848539322.issue29325@psf.upfronthosting.co.za>
2017-01-20 04:35:55malinlinkissue29325 messages
2017-01-20 04:35:55malincreate