-
Notifications
You must be signed in to change notification settings - Fork 18
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
GeoVector.__eq__crash on inconsistent types #123
Comments
@penguinolog is it common practice to return |
It's common practice to make simple compare for equality and separately make type check. |
This is an upstream issue:
I will open issue there. |
Upstream response was "this is expected". Anyway, I would say this is also our fault in the Lines 431 to 438 in 7c4d75e
|
This is similar to what attrs does: http://www.attrs.org/en/stable/why.html#hand-written-classes |
`NotImplemented` in return means: other side should try to compare, it's
the best realization
пн, 27 авг. 2018 г., 20:20 Juan Luis Cano Rodríguez <
[email protected]>:
… This is similar to what attrs does:
http://www.attrs.org/en/stable/why.html#hand-written-classes
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APSmM--0tN4TFYI2s_yDV1HsDDMpPBffks5uVDhRgaJpZM4V8wY5>
.
|
Expected behavior and actual behavior
will crush with
AttributeError
instead of returnFalse
OS independent, version = trunk.
The text was updated successfully, but these errors were encountered: