-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gerhard Häring wrote: > Maciej Fijalkowski wrote: >>> That was more a proof-of-concept (*). Without deep ctypes wizardry I >>> couldn't make anything with callbacks from SQLite work reliably. That's >>> why create_function, create_aggregate and friends were removed. If it's >>> possible to make that work at all, it's beyond my understanding of ctypes. >>> >> Hi Gerhard. > >> We tackled the issue by creating closures instead of py_object. This >> way it's saner and does not segfault for example on django test suite. >> We temporarily commited it to svn branch on codespeak, here: >> http://codespeak.net/svn/user/fijal/pysqlite2/, but we would rather >> prefer to keep it in your mercurial branch. Do you think our changes >> makes any sense? If so, can we have a commit permissions on mercurial >> branch? Otherwise, we'll at least try to keep it in sync. > > I'll need to send the username / password in encrypted form. Do you have > a PGP key?
I'll happily set up authentication on my public pysqlite repository so you guys can have commit permissions. But I won't send sensitive information in cleartext, so if you're still interested, do you have a PGP key or anything? - -- Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIMRY5dIO4ozGCH14RAqbzAJ46HF3VA4Nflq1UaGN5l4iLJwg+tQCgrHa7 yq3VYKKciAD4V3CdVljtiOA= =bjaf -----END PGP SIGNATURE----- _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
