Re: [Python-Dev] Some RFE for review

2005-07-16 Thread Reinhold Birkenfeld
Reinhold Birkenfeld wrote: > Hi, > > while bugs and patches are sometimes tricky to close, RFE can be very easy > to decide whether to implement in the first place. So what about working a > bit on this front? Here are several RFE reviewed, perhaps some can be > closed ("should" is always from sub

Re: [Python-Dev] Some RFE for review

2005-06-27 Thread Nick Coghlan
Oren Tirosh wrote: > An infrastructure that could be leveraged is the readahead buffer used > by the file object's line iterator. That's the infrastructure I meant. I was just being sloppy with my terminology ;) Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --

Re: [Python-Dev] Some RFE for review

2005-06-27 Thread Oren Tirosh
On 6/27/05, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Reinhold Birkenfeld wrote: > > 1152248: > > In order to read "records" separated by something other than newline, file > > objects > > should either support an additional parameter (the separator) to > > (x)readlines(), > > or gain an addition

Re: [Python-Dev] Some RFE for review

2005-06-27 Thread Raymond Hettinger
[Paul Moore on readline getting a record separator argument] > As a more general approach, would it be worth considering an addition > to itertools which took an iterator which generated "blocks" of items, > and split them on a subsequence? Nope. Assign responsibility to the class that has all o

Re: [Python-Dev] Some RFE for review

2005-06-27 Thread Paul Moore
On 6/27/05, Nick Coghlan <[EMAIL PROTECTED]> wrote: > As Douglas Alan's sample implementation (and his second attempt [1]) > show, getting this right (and reasonably efficient) is actually a > non-trivial exercise. Leveraging the existing xreadlines > infrastructure is an idea worth considering. >

Re: [Python-Dev] Some RFE for review

2005-06-27 Thread Nick Coghlan
Reinhold Birkenfeld wrote: > 1152248: > In order to read "records" separated by something other than newline, file > objects > should either support an additional parameter (the separator) to > (x)readlines(), > or gain an additional method which does this. > Review: The former is a no-go, I thin

Re: [Python-Dev] Some RFE for review

2005-06-26 Thread Raymond Hettinger
> 1193128: > str.translate(None, delchars) should be allowed and only delete delchars > from the string. I had agreed to this one and it's on my todo list to implement. > 1214675: > warnings should get a removefilter() method. An alternative would be to > fully document the "filters" attribute t

[Python-Dev] Some RFE for review

2005-06-26 Thread Reinhold Birkenfeld
Hi, while bugs and patches are sometimes tricky to close, RFE can be very easy to decide whether to implement in the first place. So what about working a bit on this front? Here are several RFE reviewed, perhaps some can be closed ("should" is always from submitter's point of view): 1193128: str.