> > Does anyone think changin string.atoi is the wrong way to go? > > Yes, because it changes the semantics. string.atoi() would suddenly > start to accept non-strings like integers, floats, etc. > > My suggestion would be to carefully reconsider the changes to > _tkinter. If it's true that a method can now return strings *and* > integers which previously only returned strings, then such a > change is clearly not backward compatible. I'd create a new > method for the new semantics in that case. That's my gut feeling too. --Guido van Rossum (home page: http://www.python.org/~guido/)
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