Hi Anto,
On Sun, Aug 14, 2011 at 10:50 AM, Antonio Cuni wrote:
> why is this needed? Does the sqlite API requires that the SQL buffer stays
> alive even after the call to sqlite3_prepare?
Yes, because the output argument 'next_value' receives a pointer to
the middle of the same buffer that was p
Hello List,
I'm currently experimenting with a piece of software I've recently started
maintaining, which is a cellular automaton simulation software. It's supposed to
make experimenting easy, but still be fast at simulating. As you might know, all
cellular automatons operate in steps, where usual
On 13/08/11 22:15, arigo wrote:
Log:Fix a bug in _sqlite3.py: memory is freed too early
diff --git a/lib_pypy/_sqlite3.py b/lib_pypy/_sqlite3.py
--- a/lib_pypy/_sqlite3.py
+++ b/lib_pypy/_sqlite3.py
@@ -891,7 +891,8 @@
self.statement = c_void_p()
next_char = c_char_p()
