On Sun, 2003-09-14 at 18:08, Martin v. Löwis wrote: > "Raymond Hettinger" <python at rcn.com> writes: > > > In this particular case, we are (IMHO) much better off adding an > > iterable interface than leaving current situation with "db.first()" > > and "while 1: db.next()" wrapped in a try/except for an > > undocumented exception class -- yuck. > > As nobody has protested against this specific change (yet?), I guess > you can go ahead and apply it. In doing so, you have to accept the > burden of taking blame in case this turns out to be a bad idea. Perhaps we could wait to hear from Jack or Just or someone who was concerned about feature creep in maintenance releases. I think we should decide now whether to follow the policy they propose or we should drop it. Right now, it feels like it's in limbo. Jeremy
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