#25650: `GEOSGeomerty.__eq__` should use `equals` not `equals_exact`
--------------------------------------+--------------------
Reporter: sir-sigurd | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: GIS | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
{{{
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25650>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.e254f36e22b9fdf469ca9dcf29e3983b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
