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 serhiy.storchaka
Recipients Arfrever, alanmcintyre, eric.araujo, kasal, loewis, mcepl, ocean-city, pitrou, r.david.murray, serhiy.storchaka
Date 2012-12-03.17:12:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354554765.24.0.897777657504.issue14099@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2012-12-03 17:12:45serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, alanmcintyre, pitrou, ocean-city, mcepl, eric.araujo, Arfrever, r.david.murray, kasal
2012-12-03 17:12:45serhiy.storchakasetmessageid: <1354554765.24.0.897777657504.issue14099@psf.upfronthosting.co.za>
2012-12-03 17:12:45serhiy.storchakalinkissue14099 messages
2012-12-03 17:12:45serhiy.storchakacreate