Changes between Version 47 and Version 48 of PySqlite

Timestamp:

Dec 14, 2009, 11:49:42 AM (14 years ago)

Author:

Christian Boos

Comment:

#DownloadingSQLite separately is not really necessary anymore

PySqlite

@@ -25 +25 @@
 [http://www.sqlite.org/download.html SQLite download] page.
 
+But you don't need to download it by yourself, 
+if you install the pysqlite bindings from a package, it 
+will usually come with the SQLite code bundled.
+
+If you build the pysqlite bindings by yourself, you also
+have the possibility to use the `build_static` mode, which
+will download the latest "amalgamation" code of SQLite and
+build it together with the extension code.
+
+
 ==== Building SQLite yourself ====
+
+If you really insist in being in full control...
+
 '''Note:''' If you want to use Trac in a multi-threaded setup
 by using either TracModPython or TracStandalone, be sure to build a
 '''thread-safe version of SQLite''', by using the `--enable-threadsafe` 
 configuration switch.
+
 If you use a non thread-safe library, which is unfortunately what you
 get by default on non-windows platforms, you face the risk to get 
@@ -36 +50 @@
 === The Pysqlite2 bindings ===
 
-The latest stable version available at pysqlite.googlecode.com as of this writing is '''2.5.5''', and it works fine with Trac.
+The latest stable version available at pysqlite.googlecode.com as of this writing is '''2.5.6''', and it works fine with Trac.
 
 {{{
@@ -79 +93 @@
 ==== Building pysqlite ====
 
-The recommended way to build the SQLite bindings is to do a "static build",
+The recommended way to build the SQLite bindings is to do a `static_build`,
 which will download the latest sqlite3 amalgamation file, build and link it inside
 the pysqlite module: