#25650: `GEOSGeomerty.__eq__` should use `equals` not `equals_exact`
-------------------------------------+-------------------------------------
Reporter: sir-sigurd | Owner: sir-
Type: | sigurd
Cleanup/optimization | Status: assigned
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by sir-sigurd):
Replying to [comment:2 claudep]:
> See also the discussion on #25446. The difficulty here is to find an
acceptable compatibility path and to take into account backend
differences. Feel free to try!
`GEOSGeometry` also supports comparison with WKT strings, which works like
this:
{{{
In [25]: Point(0, 0) == 'POINT (0.0000000000000000 0.0000000000000000)'
Out[25]: True
In [26]: Point(0, 0) == 'POINT (0 0)'
Out[26]: False
}}}
I think that it would make behavior more consistent if `__eq__` created
geometry from WKT string and then used it for comparison, from other hand
I think that comparison of different types is not pythonic at all. What do
you think about this?
--
Ticket URL: <https://code.djangoproject.com/ticket/25650#comment:3>
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/068.72ddb7f4a0820d5540d689eaadc9de35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
