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 josh.r
Recipients gvanrossum, josh.r, serhiy.storchaka, steven.daprano, terry.reedy, xtreak
Date 2019-08-07.23:00:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In the docs for my PR, I mention using NotImplemented in a boolean context is deprecated, raising DeprecationWarning, and will raise TypeError in a future version of Python. Serhiy has suggested the end state might be RuntimeWarning instead of TypeError. I'm in favor of it ending up as an error, but not rigid on it. Does anyone else have a strong opinion among the following options?

1. DeprecationWarning, documented as eventual TypeError (current PR)
2. DeprecationWarning, documented as eventual RuntimeWarning
3. Immediate RuntimeWarning, no DeprecationWarning period (since a warning only causes stderr output by default, it doesn't prevent working code from working unless warnings are explicitly configured to become exceptions)
Date User Action Args
2019-08-07 23:00:18josh.rsetrecipients: + josh.r, gvanrossum, terry.reedy, steven.daprano, serhiy.storchaka, xtreak
2019-08-07 23:00:18josh.rsetmessageid: <>
2019-08-07 23:00:18josh.rlinkissue35712 messages
2019-08-07 23:00:17josh.rcreate