id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
25650	`GEOSGeomerty.__eq__` should use `equals` not `equals_exact`	Sergey Fedoseev	Sergey Fedoseev	"{{{
In [1]: from django.contrib.gis.geos import LineString

In [2]: LineString((0, 0), (1, 1)) == LineString((1, 1), (0, 0))
Out[2]: False
}}}

in psql

{{{
SELECT ST_GeomFromText('LINESTRING(0 0, 1 1)') = ST_GeomFromText('LINESTRING(1 1, 0 0)');
 ?column? 
----------
 t
(1 строка)

}}}

Using `equals` in `__eq__` will allow to get rid of some quirks in tests, such as [https://github.com/django/django/blob/ab873e7a681e62d6803a3c04a051a47335f7b93a/tests/gis_tests/geoapp/test_functions.py#L433 this].

There is related [https://trac.osgeo.org/geos/ticket/731 ticket] in GEOS trac."	Cleanup/optimization	closed	GIS	dev	Normal	wontfix			Accepted	0	0	0	0	0	0