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 aeros
Recipients aeros, docs@python, eric.araujo, ezio.melotti, jdemeyer, mdk, rhettinger, veky, willingc
Date 2019-09-02.05:45:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1567403105.67.0.510346052663.issue37934@roundup.psfhosted.org>
In-reply-to
Content
> Would it be viable to rephrase the existing section in a manner that explains the functional purpose of NotImplemented without revolving around its use case in binary special methods?

To expand further upon this, here's an initial idea for improving the first sentence:

A special value used to indicate that an operation is not supported between specific types.

The section regarding it's usage in binary special methods could potentially remain. I'm thinking the main issue here (if there is one) is that the NotImplemented constant is defined _exclusively_ from a specific use case, rather than its general purpose.
History
Date User Action Args
2019-09-02 05:45:05aerossetrecipients: + aeros, rhettinger, ezio.melotti, eric.araujo, docs@python, jdemeyer, willingc, veky, mdk
2019-09-02 05:45:05aerossetmessageid: <1567403105.67.0.510346052663.issue37934@roundup.psfhosted.org>
2019-09-02 05:45:05aeroslinkissue37934 messages
2019-09-02 05:45:05aeroscreate