➜

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 carlwgeorge
Recipients Jeremy Banks, Jim.Jewett, Mark.Bucciarelli, Ronny.Pfannschmidt, adamtj, asvetlov, aymeric.augustin, berker.peksag, bkircher, bulb, carlwgeorge, dholth, flox, ghaering, malin, monsanto, ned.deily, pitrou, python-dev, r.david.murray, scott.urban, steve.dower, torsten, tshepang, zzzeek
Date 2016-12-24.05:00:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482555613.08.0.687292083724.issue10740@psf.upfronthosting.co.za>
In-reply-to
Content 
While attempting to build a Python 3.6 RPM for RHEL/CentOS 6, I noticed the following warning.

*** WARNING: renaming "_sqlite3" since importing it failed: build/lib.linux-i686-3.6-pydebug/_sqlite3.cpython-36dm-i386-linux-gnu.so: undefined symbol: sqlite3_stmt_readonly

The resolution of this issue introduced usage of the sqlite3_stmt_readonly interface.  That interface wasn't added to sqlite until 3.7.4 (http://www.sqlite.org/releaselog/3_7_4.html).  My RPM build failed because RHEL/CentOS 6 only has sqlite 3.6.20.  I understand that Python can't support old libraries forever, but can this minimum sqlite version be noted somewhere in the documentation?
History
Date User Action Args
2016-12-24 05:00:13carlwgeorgesetrecipients: + carlwgeorge, ghaering, pitrou, ned.deily, Jeremy Banks, r.david.murray, zzzeek, asvetlov, flox, adamtj, dholth, torsten, monsanto, scott.urban, aymeric.augustin, tshepang, python-dev, Ronny.Pfannschmidt, berker.peksag, Mark.Bucciarelli, Jim.Jewett, steve.dower, malin, bulb, bkircher
2016-12-24 05:00:13carlwgeorgesetmessageid: <1482555613.08.0.687292083724.issue10740@psf.upfronthosting.co.za>
2016-12-24 05:00:13carlwgeorgelinkissue10740 messages
2016-12-24 05:00:12carlwgeorgecreate