skip at pobox.com wrote: > On Nov 25 Gerhard Haering checked in a change to the release25-maint branch: > > Author: gerhard.haering > Date: Sun Nov 25 18:40:35 2007 > New Revision: 59184 > > Modified: > python/branches/release25-maint/Modules/_sqlite/statement.c > python/branches/release25-maint/Modules/_sqlite/util.c > Log: > - Backported a workaround for a bug in SQLite 3.2.x/3.3.x versions where a > statement recompilation with no bound parameters lead to a segfault > - Backported a fix necessary because of an SQLite API change in version 3.5. > This prevents segfaults when executing empty queries, like our test suite > does. > > This bug is also present on the trunk, yet I saw no indication that he > checked in such a fix there. Gerhard's patch applies cleanly. I sent him > an email after I saw the checkin and verified that the patch worked on the > trunk, but have yet to hear back from him. Yes, I remember. I postponed updating the trunk because I planned sync it with the lastest pysqlite release instead. I've updated my TODO list. > Is there some different method for getting sqlite changes into the trunk? ?! From my point of view it's a module like all the others, except it's also maintained externally as 'pysqlite'. -- Gerhard
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4