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 lemburg
Recipients lemburg
Date 2013-04-27.18:46:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367088365.18.0.161187485212.issue17857@psf.upfronthosting.co.za>
In-reply-to
Content
This is essentially the same issue as http://bugs.python.org/issue14572.

The following addition in Python 2.7.4 (compared to 2.7.3) reintroduced the same problem in a different place:

--- Python-2.7.3/Modules/_sqlite/util.h 2012-04-10 01:07:33.000000000 +0200
+++ Python-2.7.4/Modules/_sqlite//util.h        2013-04-06 16:02:36.000000000 +0200
@@ -33,6 +33,10 @@ int pysqlite_step(sqlite3_stmt* statemen
 /**
  * Checks the SQLite error code and sets the appropriate DB-API exception.
  * Returns the error code (0 means no error occurred).
  */
 int _pysqlite_seterror(sqlite3* db, sqlite3_stmt* st);
+
+PyObject * _pysqlite_long_from_int64(sqlite3_int64 value);
+sqlite3_int64 _pysqlite_long_as_int64(PyObject * value);
+
 #endif

The fix is the same as for the 2.7.3 issue: replace sqlite3_int64 with sqlite_int64
History
Date User Action Args
2013-04-27 18:46:05lemburgsetrecipients: + lemburg
2013-04-27 18:46:05lemburgsetmessageid: <1367088365.18.0.161187485212.issue17857@psf.upfronthosting.co.za>
2013-04-27 18:46:05lemburglinkissue17857 messages
2013-04-27 18:46:04lemburgcreate