Remove misleading comment about type-class unification.
This commit is contained in:
parent
402cc242f0
commit
c01b6aeede
|
@ -1,12 +1,11 @@
|
||||||
\section{Built-in Types \label{types}}
|
\section{Built-in Types \label{types}}
|
||||||
|
|
||||||
The following sections describe the standard types that are built into
|
The following sections describe the standard types that are built into
|
||||||
the interpreter. Historically, Python's built-in types have differed
|
the interpreter.
|
||||||
from user-defined types because it was not possible to use the built-in
|
\note{Historically (until release 2.2), Python's built-in types have
|
||||||
types as the basis for object-oriented inheritance. With the 2.2
|
differed from user-defined types because it was not possible to use
|
||||||
release this situation has started to change, although the intended
|
the built-in types as the basis for object-oriented inheritance.
|
||||||
unification of user-defined and built-in types is as yet far from
|
This limitation does not exist any longer.}
|
||||||
complete.
|
|
||||||
|
|
||||||
The principal built-in types are numerics, sequences, mappings, files
|
The principal built-in types are numerics, sequences, mappings, files
|
||||||
classes, instances and exceptions.
|
classes, instances and exceptions.
|
||||||
|
|
Loading…
Reference in New Issue