Changes between Version 2 and Version 3 of DjangoOnWindows

Timestamp:

Jun 29, 2008, 8:20:35 PM (16 years ago)

Author:

Ramiro Morales

Comment:

Update, describe another test suite failure on this platform

DjangoOnWindows

@@ -9 +9 @@
 As of r7787 the test suite is failing in two places when run on Windows + Python 2.5.2:
 
- * If setuptools is installed, on a test from {{{tests/regressiontests/templates/loaders.py}}} related to trying to load a template from an egg (from a report on #django-dev, it seems this is a test that is also failing on OS X).
- * On a test query from ({{{tests/regressiontests/queries/models.py}}}) when using the sqlite3 Django DB backend
+ * If setuptools is installed, on a test from {{{tests/regressiontests/templates/loaders.py}}} related to trying to load a template from an egg (from a report on #django-dev, it seems this test also fails on OS X).
+ * On a test from {{{tests/regressiontests/queries/models.py}}} when using the sqlite3 Django DB backend
 
 === tests/regressiontests/templates/loaders.py ===
 
-TBD
+When setuptools is installed (tested with version 0.6c8), the unittest contained in this file fails. Error is:
+
+{{{
+======================================================================
+ERROR: A template can be loaded from an egg
+----------------------------------------------------------------------
+Traceback (most recent call last):
+  File "C:\ramiro\django-trunk\tests\regressiontests\templates\loaders.py", line 82, in test_existing
+    contents, template_name = lts_egg("y.html")
+  File "C:\ramiro\django-trunk\django\template\loaders\eggs.py", line 24, in load_template_source
+    raise TemplateDoesNotExist, template_name
+TemplateDoesNotExist: y.html
+}}}
+
+TO BE DONE: Investigate this further.
+
+==== Workaround ====
+
+Uninstall setuptools. On [7751], Adrian modified the test suite machinery to skip the test(s) that depend on setuptools when it isn't installed.
 
 === tests/regressiontests/queries/models.py ===
 
-This test from {{{tests/regressiontests/queries/models.py}}} fails when running test suite:
+This test fails:
 
 {{{
@@ -68 +86 @@
 }}}
 
-This is a minimal models.py that shows the problem (extracted from the above regression test):
+A minimal models.py that shows the problem (extracted from the above regression test):
 
 {{{
@@ -114 +132 @@
 }}}
 
-Problems seems to be related to some bug in the version of pysqlite2 or sqlite3 (main suspect) included with the official Python 2.5.2 win32 installer (2.3.2 and 3.3.4 respectively):
+Problem seems to be related to some bug in the version of pysqlite2 or sqlite3 (main suspect) included with the official Python 2.5.2 win32 installer (2.3.2 and 3.3.4 respectively):
 
 {{{
@@ -150 +168 @@
 ==== How does this affect Django ====
 
-The problem doesn't lie with Django, but leads to ask if the order being used to try loading the sqlite-related DB-API2 modules by the sqlite3 backed ({{{django/db/backends/sqlite3/base.py}}}) shouldn't be inverted: Try loading pysqlite2 first and if it fails then try loading sqlite3:
+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:
 
 {{{
@@ -178 +196 @@
 }}}
 
-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. This might be true regardless of the platform.
+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.
 
 == See also ==