#26083: Python 2 deprecation warnings for classes that define __eq__() but not
__hash__()
--------------------------------------+------------------------------------
Reporter: atombrella | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | 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
--------------------------------------+------------------------------------
Changes (by timgraham):
* stage: Unreviewed => Accepted
Comment:
From what I read [http://stackoverflow.com/questions/15471333/how-to-
eliminate-a-python3-deprecation-warning-for-the-equality-operator on
stackoverflow], the lack of `__hash__()` is only a problem if these
objects are used in something like a `set()`, which seems unlikely in
these cases which is why we haven't had any report of problems, I suppose.
If I could at least reproduce the warnings I would find some value in
fixing them, but I can't.
--
Ticket URL: <https://code.djangoproject.com/ticket/26083#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.1874649d0398657bfd632f7ace6555c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
