Re: extended_setup.py MIA?
Gerhard Häring <[email protected]>
| Newsgroups | gmane.comp.python.db.pysqlite.user |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Patrick Phalen wrote: > Hello, > > I've just downloaded pysqlite 2.3.4. > > SQLite 3.4.0 has just been released with important bug fixes. It also > now publishes the amalgamated source and header as a separate zipped > file, which I've obtained and copied into the pysqlite directory. > > 1. I'm interested in trying the amalgamated static build. Potential > marginal speed improvements are hinted at on sqlite.org > <http://sqlite.org>. Would you expect such improvements for pysqlite > built statically? [...] I'd expect it to be perhaps < 1 % in artificial benchmarks. And not measurable in real-life apps. If you want better performance, you should look into optimizing your query plans or your own code first, if nothing else will help, then you can look into SQLite's PRAGMA commands, and if you have 5 % of performance left that you absolutely need, then you can look into compiling SQLite with better compiler options with the amalgamation. > 2. Instructions are to issue 'python extended_setup.py build_static'. I > don't find extended_setup.py in the pysqlite 2.3.4 source. Where is it? It was in Subversion only. I've uploaded a fixed source release now. - -- Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGeE5OdIO4ozGCH14RAqEcAKCkT7FezpcYsUboUYG/jlVBUQ5CtQCeMPBL 7yCjm7+xT9X94X9mR/UHUUM= =VkQF -----END PGP SIGNATURE-----