STINNER Victor added the comment: >> The function was already documented in Python 3.5, so please add a ".. >> versionchanged:: 3.6" to document the API chnange.
> No, this behavior is not documented in any released Python version. The note > about the failure was added in issue28701. Ah wait, you want to push this change into Python 3.5? I would prefer to leave Python 3.5 unchanged. Even if you modify Python 3.5, you still have to mention the "versionchanged", since it's a behaviour change. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28808> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
