Josh Rosenberg <shadowranger+pyt...@gmail.com> added the comment:
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) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35712> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
