On Sat, 28 Apr 2001, Tim Peters <tim_one@users.sourceforge.net> wrote:
> Modified Files:
> bltinmodule.c
> Log Message:
> Fix buglet reported on c.l.py: map(fnc, file.xreadlines()) blows up.
> Also a 2.1 bugfix candidate (am I supposed to do something with those?).
> Took away map()'s insistence that sequences support __len__, and cleaned
> up the convoluted code that made it *look* like it really cared about
> __len__ (in fact the old ->len field was only *used* as a flag bit, as
> the main loop only looked at its sign bit, setting the field to -1 when
> IndexError got raised; renamed the field to ->saw_IndexError instead).
Can anyone give me his opinion about whether 2.0.1 should have this
bug fix? It's not just for file.xreadlines(): the older fileinput.fileinput()
is hurt by this as well...
--
"I'll be ex-DPL soon anyway so I'm |LUKE: Is Perl better than Python?
looking for someplace else to grab power."|YODA: No...no... no. Quicker,
-- Wichert Akkerman (on debian-private)| easier, more seductive.
For public key, finger moshez@debian.org |http://www.{python,debian,gnu}.org
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