Guido van Rossum wrote: > >... > > While it will admittedly take a while, the intention of string methods > was to eventually phase out the string module. So TOOWTDI is only > violated during the transition. Why wouldn't a similar strategy work for length and string attributes? >... > Personally, I don't think that the "problem" this change is addressing > is worth asking everybody to change their code -- so we'd have live > with len(x) and x.len() as viable ways to ask for x's length > *forever*, violating TOOWTDI permanently. I don't like that. How was the string methods problem more serious than this one? I'm not trying to be difficult: I really don't perceive a difference. -- Take a recipe. Leave a recipe. Python Cookbook! http://www.ActiveState.com/pythoncookbook
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