This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author francescor
Recipients eric.araujo, francescor, javawizard, lregebro, python-dev, rhettinger
Date 2011-04-20.14:23:07
SpamBayes Score 7.63373e-12
Marked as misclassified No
Message-id <>
I think the whole issue is indeed how NotImplemented is treated. To me saying that 'not NotImplemented' is True is wrong. About the stack overflow I found there are various possible fixes, however none will nice.

By definition, NotImplemented is the way that a method or operation have to signal to the interpreter that it doesn't know how to handle given operand types. IMHO, it shouldn't be possible to receive NotImplemented as operand value, and it shouldn't have a boolean value. Indeed, t should be handled as a special case by the interpreter.

To go further, I am not really sure that NotImplemented should be a return value. Probably, an exception that is trapped by the interpreter when evaluating an expression would be easier to define and handle.

Of course, such a change should be deeply grokked before being put in place, also because of the high impact on code that already relies on NotImplemented having a value.
Date User Action Args
2011-04-20 14:23:09francescorsetrecipients: + francescor, rhettinger, eric.araujo, lregebro, python-dev, javawizard
2011-04-20 14:23:09francescorsetmessageid: <>
2011-04-20 14:23:08francescorlinkissue10042 messages
2011-04-20 14:23:07francescorcreate