➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lukasz.langa
Recipients Claudiu.Popa, barry, fdrake, lrowe, lukasz.langa, python-dev, rbcollins, serhiy.storchaka
Date 2016-05-02.23:05:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462230337.35.0.902750512087.issue21159@psf.upfronthosting.co.za>
In-reply-to
Content 
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?
History
Date User Action Args
2016-05-02 23:05:37lukasz.langasetrecipients: + lukasz.langa, fdrake, barry, rbcollins, Claudiu.Popa, lrowe, python-dev, serhiy.storchaka
2016-05-02 23:05:37lukasz.langasetmessageid: <1462230337.35.0.902750512087.issue21159@psf.upfronthosting.co.za>
2016-05-02 23:05:37lukasz.langalinkissue21159 messages
2016-05-02 23:05:36lukasz.langacreate