Code

Changes between Version 12 and Version 13 of DjangoOnWindows


Ignore:
Timestamp:
09/03/08 05:09:14 (6 years ago)
Author:
ramiro
Comment:

#8196 was fixed in [8842], update proposals, revision. Restore page focus

Legend:

Unmodified
Added
Removed
Modified
  • DjangoOnWindows

    v12 v13  
    1 = Django on Windows (bugs actually caused by Sqlite <3.3.6 and absence of PIL) = 
     1= Django on Windows = 
    22 
    33(work in progress) 
     
    99=== Test suite failures === 
    1010 
    11 The following test suite failures affect Django under Windows (XP 32 bits) + official Python 2.5.2 (includes SQLite 3.3.4, excludes PIL) 
     11As of r8889 (1.0rc1), the test suite is showing the following failure(s) when run under Windows (XP 32 bits) + official Python 2.5.2: 
    1212 
    13 As of r8747, the test suite is showing the following failures when run on sqlite <3.3.6: 
     13 * Ticket #7570 when using the sqlite3 Django DB backend (official Python 2.5.2 Windows distribution includes SQLite 3.3.4). 
    1414 
    15  * Ticket #7570 on a test from {{{tests/regressiontests/queries/models.py}}} when using the sqlite3 Django DB backend. 
     15==== ticket #7570 ==== 
    1616 
    17 As of r8747, the test suite is showing the following failures when run without PIL: 
    18  
    19  * Ticket #8196 on a test from {{{tests/modeltests/model_forms/models.py}}} 
    20  
    21 ==== tests/regressiontests/queries/models.py ==== 
    22  
    23 This has been reported as ticket #7570. 
    24  
    25 This test fails: 
     17This test (and other two similar tests) fails: 
    2618 
    2719{{{ 
     
    108100 
    109101    def __unicode__(self): 
     102 
    110103        return self.name 
    111104}}} 
     
    150143===== Possible solution ===== 
    151144 
    152 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. 
     145As the table above shows, version <= 3.3.4 of sqlite seems to be affected by this bug whilst version >=3.3.6 isn't. 
    153146 
    154147We think it's a SQLite bug reported in [http://www.sqlite.org/cvstrac/tktview?tn=1768 this] ticket and fixed in [http://www.sqlite.org/cvstrac/chngview?cn=3173 this] commit six days after 3.3.5 was tagged, so it would be safe to assume that 3.3.5 is also affected. This is the complete changelog between 3.3.4 and 3.3.6: http://www.sqlite.org/cvstrac/timeline?d=115&e=2006-Jun-06&c=2&px=&s=9&dm=1&x=1 
     
    158151===== How does this affect Django ===== 
    159152 
    160 The problem doesn't lie within Django itself, but leads to ask oneself if the order being used by the sqlite3 backed to try loading the sqlite DB-API2 modules ({{{django/db/backends/sqlite3/base.py}}}) shouldn't be inverted: Try loading pysqlite2 first and if this fails then try loading sqlite3: 
     153The problem doesn't lie within Django itself, but one or both of the following proposals would help users solve this problem: 
     154 
     155 * Document the fact that SQLite 3.3.6 is needed. As of now Windows users using stable, supported, non-beta versions of python need to be directed to also manually apply the patch below to their copies of Django. 
     156 * Invert the order being in which the sqlite3 backend tries loading the sqlite DB-API2 modules ({{{django/db/backends/sqlite3/base.py}}}) to try loading pysqlite2 first and if this fails then try loading sqlite3. Reasoning behind this is that this would allow the user to take advantage of newer pysqlite2/sqlite3 versions he/she may have installed even if using Python 2.5.x. This might be true and desirable regardless of platform: 
    161157 
    162158{{{ 
     
    186182}}} 
    187183 
    188 Reasoning behind this is that this would allow the user to take advantage of newer pysqlite2/sqlite3 versions he/she may have installed even if using Python 2.5.x. This might be true and desirable regardless of platform. 
    189  
    190184== Deployment == 
    191185