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
Remove redundant __ne__ implementations #67515
Comments
As far as default __ne__ implementation delegates to __eq__, concrete __ne__ implementations are mostly redundant. They make sens when default __ne__ did not handle non-comparable types correctly, but now it is fixed. Proposed patch removes correct but redundant __ne__ implementations (incorrect implementations were removed in bpo-21408). |
I looked at all the instances of __ne__() identified in the patch, and they all seem redundant with the __eq__() implementations, so I think this patch is good. |
New changeset 3603bae63c13 by Serhiy Storchaka in branch 'default': |
Thanks Martin and Georg for your reviews. |
Nice work. |
I'm a little surprised you didn't get pushback from asyncio (i.e. Victor). We try to keep the source identical across releases while asyncio is in provisional mode (i.e. until 3.5 is released). |
Should I restore __ne__ in asyncio? The version without __ne__ will work with Python 3.4.3 because bpo-21408 patch was committed in 3.4 too. Explicit __ne__ implementation is just redundant. |
Yeah, I'd like to see it restored in asyncio. It seems to be just one file On Mon, Mar 30, 2015 at 10:38 AM, Serhiy Storchaka <report@bugs.python.org>
|
New changeset e881444f078f by Serhiy Storchaka in branch 'default': |
Thanks! On Mon, Mar 30, 2015 at 12:26 PM, Roundup Robot <report@bugs.python.org>
|
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: