[Anna Ravenscroft] >>>> I think this is a really good point. next() is supposed to get used, by >>>> coders, in regular code - so it shouldn't be __next__. I can understand the >>>> desire for both forms, although that seems it would clutter things up >>>> unnecessarily - particularly if the two do the same thing [Phillip] >>> By this argument, we should be using ob.len() instead of len(ob), and >>> ob.iter() instead of iter(ob). [Oleg] >> Yes, I think it'd be more consistent and more object-oriented. After all >> we've switched from string.split(x, y) to x.split(y)... [Raymond Hettinger] > LOL, Shakespearean comedy on python-dev: > > * Phillip mistates Anna's position and shoots down a straw-man. > * Oleg agrees with a literal reading of Phillips note, missing the sarcasm > entirely. Then * Raymond points out those foibles in a humorous way. * Uncle Timmy replies in fashion that's hard to understand, although some suspect he's insinuating that all missed the point ;-) How's everyone doing, BTW? I think I picked up the Texas Mystery Disease from Holger Krekel -- bed-ridden 20 hours Saturday, and most of Sunday, with dry cough and high fever. Or that's just a normal outcome of sprinting :-)
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