Changes between Version 5 and Version 6 of DjangoOnWindows

Timestamp:

Jun 30, 2008, 7:20:10 PM (16 years ago)

Author:

Ramiro Morales

Comment:

More info, summarize

DjangoOnWindows

@@ -145 +145 @@
 }}}
 
-The win32 installer for Python 2.5 has the same combination of pysqlite/sqlite versions and exhibits the same problem:
-
-{{{
-#!python
-Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit (Intel)] on win32
-Type "help", "copyright", "credits" or "license" for more information.
->>> from sqlite3 import dbapi2
->>> print dbapi2.version_info
-(2, 3, 2)
->>> print dbapi2.sqlite_version_info
-(3, 3, 4)
-}}}
-
-The same test works flawlessly on the following platforms:
- * Python 2.4.4 + pysqlite2 2.3.2 + sqlite3 3.3.8 (GNU/Debian Linux 4.0)
- * Python 2.5 + builtin pysqlite2 ''aka'' sqlite3 2.3.2 + sqlite3 3.3.8 (GNU/Debian Linux 4.0)
- * Python 2.5.2 + builtin pysqlite2 ''aka'' sqlite3 2.3.2 + sqlite3 3.5.9 (GNU/Debian Linux Sid as of Jun 29, 2008)
-this may be thanks to the fact that on these platforms the shared sqlite3 library being used by the pysqlite2 (Python 2.4) or sqlite3 (Python 2.5) Python modules is the system wide one and so it hasn't been frozen at 3.3.4.
+The win32 installer for Python 2.5 ships the same combination of pysqlite/sqlite versions and exhibits the same problem. The tests were also run under some other Windows- and Linux-based scenarios.
+
+Summarizing:
+
+|| '''Platform''' || '''Python version''' || '''pysqlite2 version''' || '''sqlite version''' || '''works?''' || '''Notes''' ||
+|| win32          || 2.4.4                || 2.3.0 (external)        || 3.3.6                || YES          ||             ||
+|| Debian Linux   || 2.4.4                || 2.3.2 (external)        || 3.3.8                || YES          ||             ||
+|| win32          || 2.5                  || 2.3.2 (built-in sqlite3)|| 3.3.4                || NO           ||             ||
+|| Debian Linux   || 2.5                  || 2.3.2 (built-in sqlite3)|| 3.3.8                || YES          ||             ||
+|| win32          || 2.5.2                || 2.3.2 (built-in sqlite3)|| 3.3.4                || NO           ||             ||
+|| win32          || 2.5.2                || 2.4.1 (external)        || 3.5.2                || YES          || '''*'''     ||
+|| Debian Linux   || 2.5.2                || 2.3.2 (built-in sqlite3)|| 3.5.9                || YES          ||             ||
+
+As is can be seen, the test under Linux were always successful, this may be due to the fact that on these platforms the shared sqlite3 library being used by the pysqlite2 (Python 2.4) or sqlite3 (Python 2.5) Python modules is the system wide one and so it hasn't been frozen at 3.3.4.
 
 ==== Possible solution ====
 
-As sqlite/pysqlite development continues, the pysqlite project keeps publishing new win32 binary installers for Python 2.5. Latest as of today June 29, 2008 is version 2.4.1 ({{{pysqlite-2.4.1.win32-py2.5.exe}}}) that uses sqlite version 3.5.2:
-
-{{{
-#!python
->>> from pysqlite2 import dbapi2
->>> print dbapi2.version_info
-(2, 4, 1)
->>> print dbapi2.sqlite_version_info
-(3, 5, 2)
->>>
-}}}
-
-The error doesn't show itself when running the tests if one manages to force Django to use this newer version of pysqlite (see below). This seems to indicate that something was fixed on sqlite between versions 3.3.4 and 3.5.2 (see http://sqlite.org/changes.html).
+As the table above shows, version 3.3.4 of sqlite seems to be affected by this bug whilst version 3.3.6 isn't (see http://sqlite.org/changes.html for possible hints).
+
+As sqlite/pysqlite development continues, the pysqlite project keeps publishing new win32 binary installers for Python 2.5. Latest as of today June 29, 2008 is version 2.4.1 ({{{pysqlite-2.4.1.win32-py2.5.exe}}}) that uses sqlite version 3.5.2 (see entry marked with '''*''' in the table above.)
 
 ==== How does this affect Django ====