-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Change map to geo_equals #2956
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tests are failing; also pls add a release note
| @pytest.mark.xfail_unsupported | ||
| def test_geo_equals(backend, geo): | ||
| """ | ||
| Test geo_equals/equals. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reference the issue in a comment. the Notes section is not needed here
|
@jreback thanks for the review. I added the release note and also changed 2 tests that were using I also updated the documentation about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
| assert expr.execute().all() | ||
|
|
||
| expr = geotable.geo_point.geo_equals(geotable.geo_linestring) | ||
| assert not expr.execute().all() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want all them to be different? Then any should be better I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that makes sense. I will change it now. thanks @datapythonista
|
thanks @xmnlab |
This PR fix the problem with
geo_equals.Currently,
equalsoperation is mapped togeo_equalsand it is given problems as reported at #2197Fix #2197