Anders Blomdell added the comment:
> So my suggestion is to remove in "pysql_connection_commit" the call to :
> pysqlite_do_all_statements(self, ACTION_RESET, 0);
> to bring back the correct old behavior.
That's what I have been running for years, now...
> And a
Anders Blomdell added the comment:
The culprit seems to be 'pysqlite_do_all_statements(self, ACTION_RESET, 0)' in
pysqlite_connection_commit, which resets all active statements, but subsequent
fetch/fetchall seems to trash the sqlite3 state in the statements. Removing the
ACTION_R
New submission from Anders Blomdell :
With version 2.7 (and 2.7.1rc1), the following sequence (see attached test):
c = cursor.execute(' select k from t where k == ?;', (1,))
conn.commit()
r = c.fetchone()
Traceback (most recent call last):
File "/bugs/sqlite_bug.p
New submission from Anders Blomdell :
While trying to get a PEP302 import hook to function properly, I found
that the default traceback picks up the wrong sourcecode for PEP302
loaded modules.
The testcase pep302_traceback.py tries to emulate the behavior of the
files in ordinary, which
