[issue1393] function comparing lacks NotImplemented error

Guido van Rossum added the comment: That solution (return NotImplemented instead of False) appears to work. Committed revision 59761. Thanks for bringing up this regression w.r.t. 2.5! -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PR

[issue1393] function comparing lacks NotImplemented error

Paul Pogonyshev added the comment: I'd like to ping this issue as I think it is important enough (core is affected). __ Tracker <[EMAIL PROTECTED]> __ __

[issue1393] function comparing lacks NotImplemented error

Changes by Gabriel Genellina: -- nosy: +gagenellina __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue1393] function comparing lacks NotImplemented error

Guido van Rossum added the comment: It's still odd though. Why does object() == Anything() pass control to the right hand side, while (lambda: None) == Anything() doesn't? There's no definition of equality in PyFunction_Type, so it would seem to fall back on the definition in PyBaseObject_Type,

[issue1393] function comparing lacks NotImplemented error

Christian Heimes added the comment: Additional prints make it easy to understand what happens here: >>> class Anything: ... def __eq__(self, other): ... print("eq") ... return True ... def __ne__(self, other): ... print("ne") ... return False ... >>> x = l

[issue1393] function comparing lacks NotImplemented error

Guido van Rossum added the comment: Odd. I'll look into it. -- assignee: -> gvanrossum nosy: +gvanrossum priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1393] function comparing lacks NotImplemented error

New submission from Paul Pogonyshev: I believe attached script demonstrates a bug in Python 3000. As far as I can tell, it should print four times 'True'. -- components: Interpreter Core files: test.py messages: 57135 nosy: Paul Pogonyshev severity: normal status: open title: function c