> Guido: > > > > if the only reason for it is to use isinstance? > > > > So that an extension author *could* write an int-like type deriving > > from it? > > But didn't you just say that people shouldn't be > deriving their own int-like types from baseinteger? Indeed, in general they shouldn't. But for specialized purposes it might be needed (that's why I emphasized *could*). Unfortunately, for the purpose of having one's ersatz integers accepted as the real thing by the Python core, you pretty much have to inherit from int. So my only reason to make baseinteger a class rather than a tuple is consistency with basestring. --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