Raymond Hettinger added the comment: > However, doing the check on 'other' and raising a TypeError > with an appropriate message would still be better
Let's be clear. These are duck-typed methods. A type check is inappropriate. Anything with o.items() is allowed regardless of type. Also, I generally won't approve changes to existing APIs without compelling real-world use cases to motivate the design change. Otherwise, you just create unnecessary churn and consternation. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22766> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
