Re: converting a sed / grep / awk / . . . bash pipe line into python
- From: bearophileHUGS@xxxxxxxxx
- Date: Wed, 3 Sep 2008 05:23:10 -0700 (PDT)
Roy Smith:
No reason to limit how many splits get done if you're
explicitly going to slice the first two.
You are probably right for this problem, because most lines are 2
items long, but in scripts that have to process lines potentially
composed of many parts, setting a max number of parts speeds up your
script and reduces memory used, because you have less parts at the
end.
Bye,
bearophile
.
- References:
- Re: converting a sed / grep / awk / . . . bash pipe line into python
- From: Peter Otten
- Re: converting a sed / grep / awk / . . . bash pipe line into python
- From: Roy Smith
- Re: converting a sed / grep / awk / . . . bash pipe line into python
- Prev by Date: Re: converting a sed / grep / awk / . . . bash pipe line into python
- Next by Date: new python docs
- Previous by thread: Re: converting a sed / grep / awk / . . . bash pipe line into python
- Next by thread: Re: Large amount of files to parse/organize, tips on algorithm?
- Index(es):