On Mon, 1 Jan 2001, Thomas Wouters <thomas@xs4all.net> wrote: > As for speed (which stays a secondary or tertiary consideration at best) do > we really need the xreadlines method to accomplish that ? Couldn't fileinput > get almost the same performance using readlines() with a sizehint ? I <aol>me too</aol> Adding xreadlines() to the interface would break half a dozen file-objects all around the world (just the standard library has StringIO, cStringIO, GzipFile and probably some others I can't remember) Adding .readlines(sizehint) to fileinput, and adding a function to create something similar to fileinput from a file object (as opposed to a file name) would help everyone, and doesn't seem to hard. Is there a gotcha I'm just not seeing? -- Moshe Zadka <sig@zadka.site.co.il> This is a signature anti-virus. Please stop the spread of signature viruses!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4