Łukasz Langa added the comment: At this point I agree with Robert. It's public API that predates my changes which was inadequately mocked.
I've seen similar problems in the past when we've changed reading file objects to use plain iteration instead of the .readlines() method. I've had people complain that their "file-like object" implementation provided just .readlines() and suddenly stopped working. I can relate to how this caused painful churn. We do try to minimize it. However, it's hard to evolve any code if we can't touch it based on fear of breaking incompletely duck typed third-party code :( Barry, would you still like this to be reverted on Python 3.4? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21159> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
