Specific tasks, by the way: - Add a 'string' built-in type that's the common base class for str and unicode. - Make buffer, xrange, and slice into new-stype types. - Figure out which type names are commonly tested for that aren't yet built-ins, and propose a way to expose their names. - The 'new' module may also become deprecated; its functions (instance, instancemethod, function, code, module, and classobj) should be implementable by calling the appropriate types (not all of these are their own factories yet, so that's another task). Then for compatibility, a module "new.py" may be provided that implements the interfaces in a backward-compatible way. --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