[Python-Dev] Int FutureWarnings and other 2.4 TODOs

[Greg Ewing]

Guido van Rossum <guido at python.org>:

> > If you agree with this premise, then it suggests a different
> > approach. Use different implementations in C, but have type(x) in
> > Python lie.  type(x) would always return the type object which is
> > now known as "long".
> 
> If this can be made to work, I like it.  __class__ should also be
> hacked, and isinstance(); and who knows how many other places, but
> probably not too many.

What would happen under this scheme if someone did try
to subclass int, or long? What would isinstance() make of
such subclasses?

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg at cosc.canterbury.ac.nz	   +--------------------------------------+