From 84ea85fb90a3914fef9ab74b1f4f5bb919bec068 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Thu, 3 Jan 2013 17:37:40 +0100 Subject: [PATCH] Updated comment about PostGIS bug 2035 PostGIS 2.0.2 has been released on December 3rd 2012, with the fix included. --- django/contrib/gis/tests/geoapp/tests.py | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/django/contrib/gis/tests/geoapp/tests.py b/django/contrib/gis/tests/geoapp/tests.py index 8f2c22e841..a5164d39d1 100644 --- a/django/contrib/gis/tests/geoapp/tests.py +++ b/django/contrib/gis/tests/geoapp/tests.py @@ -295,10 +295,8 @@ class GeoLookupTest(TestCase): self.assertEqual(2, len(qs)) for c in qs: self.assertEqual(True, c.name in cities) - # The left/right lookup tests are known failures on PostGIS 2.0+ - # until the following bug is fixed: - # http://trac.osgeo.org/postgis/ticket/2035 - # TODO: Ensure fixed in 2.0.2, else modify upper bound for version here. + # The left/right lookup tests are known failures on PostGIS 2.0/2.0.1 + # http://trac.osgeo.org/postgis/ticket/2035 if (2, 0, 0) <= connection.ops.spatial_version <= (2, 0, 1): test_left_right_lookups = unittest.expectedFailure(test_left_right_lookups)