Serhiy Storchaka added the comment: > This idiom currently works and should not be broken.
Hmm. This seems doubtful to me, but if it is used, then I agree, it shouldn't be broken. > I guess that the slowdown by seek() is neglectable compared to this. Even one function call can have effect on performance of short reads (issue10376, issue16304). Fortunately in this corner case the read buffer will be used. > Also note that we most often seek to the current position; the OS should > notice that and return swiftly. This may affect the buffered Python file (I did not check). The OS also doesn't notice this if the OS is Windows (issue8745). I want to see and test an updated patch. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14099> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
