Mark Borgerding <mborg...@gmail.com> added the comment:
So third-party code was knowingly broken to satisfy an aesthetic notion that substitution should be more like iteration. Would not a FutureWarning have been a kinder way to stage this implementation? A foolish consistency, indeed. ---------- nosy: +Mark Borgerding _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32308> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
