Is __ne__ method autogenerated?

[INADA Naoki]

The reference says:

The truth of x==y does not imply that x!=y is false.
Accordingly, when defining __eq__(), one should also
define __ne__() so that the operators will behave as expected.

(http://docs.python.org/3/reference/datamodel.html#object.__eq__)

But I saw different behavior on 3.3:
https://gist.github.com/4231096

Could anyone teach me what happen about my code?

 

[Ian Kelly]

The reference says:

The truth of x==y does not imply that x!=y is false.
Accordingly, when defining __eq__(), one should also
define __ne__() so that the operators will behave as expected.

(http://docs.python.org/3/reference/datamodel.html#object.__eq__)

But I saw different behavior on 3.3:
https://gist.github.com/4231096

Could anyone teach me what happen about my code?

http://docs.python.org/3/whatsnew/3.0.html#operators-and-special-methods

I can't find it documented anywhere else.

 

[Chris Rebert]

The reference says:

The truth of x==y does not imply that x!=y is false.
Accordingly, when defining __eq__(), one should also
define __ne__() so that the operators will behave as expected.

(http://docs.python.org/3/reference/datamodel.html#object.__eq__)

But I saw different behavior on 3.3:
https://gist.github.com/4231096

Could anyone teach me what happen about my code?

The reference is not completely accurate in this case. See
http://bugs.python.org/issue4395
"Document auto __ne__ generation; [...]"

 

[INADA Naoki]

Thanks a million!

The reference says:

The truth of x==y does not imply that x!=y is false.
Accordingly, when defining __eq__(), one should also
define __ne__() so that the operators will behave as expected.

(http://docs.python.org/3/reference/datamodel.html#object.__eq__)

But I saw different behavior on 3.3:
https://gist.github.com/4231096

Could anyone teach me what happen about my code?

The reference is not completely accurate in this case. See
http://bugs.python.org/issue4395
"Document auto __ne__ generation; [...]"