Raymond Hettinger added the comment: FWIW, I think doc changes like this need to be made by the people most familiar with the implementation details and with the original design intent (i.e. the authors of PEP 207).
The knowledge here is fragile and it would be easy to accidentally make-up new normative rules that aren't actually true or necessary, or to subtly misrepresent what was trying to be accomplished originally. The risk is greatest when the OP is just now learning the ins and outs of NotImplemented (i.e. whether in-place operations can or should return NotImplemeted or whether those operations can be duck typed). Changing "can be returned" to "should be returned" is normative (making-up a new rule without sufficient discussion). This doesn't add explanation; instead, instead, it make a rule change about how a feature should be used. https://hg.python.org/cpython/rev/26d0a17affb5 ---------- nosy: +gvanrossum, rhettinger, tim.peters _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22780> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
