Gian-Carlo Pascutto added the comment: >Then we wait for someone that really knows why the change was done in the >first place.
Python 2.7 had a regression compared to 2.6 where a SELECT after a COMMIT would silently return the wrong data: http://bugs.python.org/issue23129 http://bugs.python.org/issue10513 Neither exiting with a locked error nor producing the wrong data are particularly appealing results. Did 2.6 pass those sets that caused the attempted fix to get backed out? ---------- nosy: +Gian-Carlo Pascutto _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29006> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
