Groups > comp.lang.python > #31993

Re: Fast forward-backward (write-read)

From	Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject	Re: Fast forward-backward (write-read)
Date	2012-10-24 01:23 -0400
Organization	> Bestiaria Support Staff <
References	(1 earlier) <CA+vVgJV6feUL0gTPC==3fp3Wq8zvRXgoyhVaUYnZNtMfF8qpLw@mail.gmail.com> <CA+vVgJWnAThHhD4cUJzXLGdVojCNA1oV_qKYwa+7UsEqS=x7XQ@mail.gmail.com> <CA+vVgJUNOZD3vBVFDXvXzdXb=c5THQG+B5dSOp_uF1nqDHhPug@mail.gmail.com> <CA+vVgJV2A7oJQCRGFypqsfYXHNVxSuhWJUhCF+FM4NWnXanGcA@mail.gmail.com> <k679kb$rs1$1@ger.gmane.org>
Newsgroups	comp.lang.python
Message-ID	<mailman.2717.1351056298.27098.python-list@python.org> (permalink)

Show all headers | View raw

On Tue, 23 Oct 2012 16:35:40 -0700, emile <emile@fenx.com> declaimed the
following in gmane.comp.python.general:

> On 10/23/2012 04:19 PM, David Hutto wrote:
> > forward =  [line.rstrip('\n') for line in f.readlines()]
> 
> f.readlines() will be big(!) and have overhead... and forward results in 
> something again as big.
>
	Well, since file objects are iterable, could one just drop the
.readlines() ? ( ... line in f )

> > backward =  [line.rstrip('\n') for line in reversed(forward)]
> 
> and defining backward looks to me to require space to build backward and 
> hold reversed(forward)
>
	And since the line-ends have already been stripped from forward,
backward should just be:

	backward = reversed(forward)
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
        wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: Fast forward-backward (write-read) Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-10-24 01:23 -0400
  Re: Fast forward-backward (write-read) Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-10-24 08:05 +0000
    Re: Fast forward-backward (write-read) Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-10-24 14:36 -0400

csiph-web