> Guido> Quit harping about the fact that types isn't deprecated already! > Guido> We haven't even done a release yet. [Skip] > I'm not. You were the one who brought up maybe deprecating it. If > it's not going to be deprecated I see no reason it should not > provide names for all the builtin types. I think everybody else sort of expects that it will be phased out -- a gentle form of deprecation -- because it's mostly redundant and having two official ways to refer to exactly the same object is somewhat unpythonic. We'll have to figure out what to do about names that are defined in types.py but are not globals; are there any of those that are actually used? I know of one useful one: StringTypes. I *think* I'd like to see that become a common base class for str and unicode. This may require a PEP. But in the mean time, while types.py is in limbo, let's not add to it. --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