Updated comment about PostGIS bug 2035
PostGIS 2.0.2 has been released on December 3rd 2012, with the fix included.
This commit is contained in:
parent
3fc43c964e
commit
84ea85fb90
|
@ -295,10 +295,8 @@ class GeoLookupTest(TestCase):
|
||||||
self.assertEqual(2, len(qs))
|
self.assertEqual(2, len(qs))
|
||||||
for c in qs: self.assertEqual(True, c.name in cities)
|
for c in qs: self.assertEqual(True, c.name in cities)
|
||||||
|
|
||||||
# The left/right lookup tests are known failures on PostGIS 2.0+
|
# The left/right lookup tests are known failures on PostGIS 2.0/2.0.1
|
||||||
# until the following bug is fixed:
|
|
||||||
# http://trac.osgeo.org/postgis/ticket/2035
|
# http://trac.osgeo.org/postgis/ticket/2035
|
||||||
# TODO: Ensure fixed in 2.0.2, else modify upper bound for version here.
|
|
||||||
if (2, 0, 0) <= connection.ops.spatial_version <= (2, 0, 1):
|
if (2, 0, 0) <= connection.ops.spatial_version <= (2, 0, 1):
|
||||||
test_left_right_lookups = unittest.expectedFailure(test_left_right_lookups)
|
test_left_right_lookups = unittest.expectedFailure(test_left_right_lookups)
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue