#30651: __eq__ should return NotImplemented when equality cannot be checked.
-------------------------------------+-------------------------------------
Reporter: Elizabeth Uselton | Owner: Elizabeth
Type: | Uselton
Cleanup/optimization | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"54ea290e5bbd19d87bd8dba807738eeeaf01a362" 54ea290e]:
{{{
#!CommitTicketReference repository=""
revision="54ea290e5bbd19d87bd8dba807738eeeaf01a362"
Fixed #30651 -- Made __eq__() methods return NotImplemented for not
implemented comparisons.
Changed __eq__ to return NotImplemented instead of False if compared to
an object of the same type, as is recommended by the Python data model
reference. Now these models can be compared to ANY (or other objects
with __eq__ overwritten) without returning False automatically.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30651#comment:9>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.90f7e7c8ee7bbcb9484ef7a283a3872b%40djangoproject.com.
