3.Data model

3.1.Objects, values and types

Objects are Python’s abstraction for data. All data in a Python programis represented by objects or by relations between objects. (In a sense, and inconformance to Von Neumann’s model of a “stored program computer”, code is alsorepresented by objects.)

Every object has an identity, a type and a value. An object’sidentity neverchanges once it has been created; you may think of it as the object’s address inmemory. Theis operator compares the identity of two objects; theid() function returns an integer representing its identity.

CPython implementation detail: For CPython,id(x) is the memory address wherex is stored.

An object’s type determines the operations that the object supports (e.g., “doesit have a length?”) and also defines the possible values for objects of thattype. Thetype() function returns an object’s type (which is an objectitself). Like its identity, an object’stype is also unchangeable.[1]

Thevalue of some objects can change. Objects whose value canchange are said to bemutable; objects whose value is unchangeable once theyare created are calledimmutable. (The value of an immutable container objectthat contains a reference to a mutable object can change when the latter’s valueis changed; however the container is still considered immutable, because thecollection of objects it contains cannot be changed. So, immutability is notstrictly the same as having an unchangeable value, it is more subtle.) Anobject’s mutability is determined by its type; for instance, numbers, stringsand tuples are immutable, while dictionaries and lists are mutable.

Objects are never explicitly destroyed; however, when they become unreachablethey may be garbage-collected. An implementation is allowed to postpone garbagecollection or omit it altogether — it is a matter of implementation qualityhow garbage collection is implemented, as long as no objects are collected thatare still reachable.

CPython implementation detail: CPython currently uses a reference-counting scheme with (optional) delayeddetection of cyclically linked garbage, which collects most objects as soonas they become unreachable, but is not guaranteed to collect garbagecontaining circular references. See the documentation of thegcmodule for information on controlling the collection of cyclic garbage.Other implementations act differently and CPython may change.Do not depend on immediate finalization of objects when they becomeunreachable (so you should always close files explicitly).

Note that the use of the implementation’s tracing or debugging facilities maykeep objects alive that would normally be collectable. Also note that catchingan exception with atryexcept statement may keepobjects alive.

Some objects contain references to “external” resources such as open files orwindows. It is understood that these resources are freed when the object isgarbage-collected, but since garbage collection is not guaranteed to happen,such objects also provide an explicit way to release the external resource,usually aclose() method. Programs are strongly recommended to explicitlyclose such objects. Thetryfinally statementand thewith statement provide convenient ways to do this.

Some objects contain references to other objects; these are calledcontainers.Examples of containers are tuples, lists and dictionaries. The references arepart of a container’s value. In most cases, when we talk about the value of acontainer, we imply the values, not the identities of the contained objects;however, when we talk about the mutability of a container, only the identitiesof the immediately contained objects are implied. So, if an immutable container(like a tuple) contains a reference to a mutable object, its value changes ifthat mutable object is changed.

Types affect almost all aspects of object behavior. Even the importance ofobject identity is affected in some sense: for immutable types, operations thatcompute new values may actually return a reference to any existing object withthe same type and value, while for mutable objects this is not allowed.For example, aftera=1;b=1,a andb may or may not refer tothe same object with the value one, depending on the implementation.This is becauseint is an immutable type, so the reference to1can be reused. This behaviour depends on the implementation used, so shouldnot be relied upon, but is something to be aware of when making use of objectidentity tests.However, afterc=[];d=[],c andd are guaranteed to refer to twodifferent, unique, newly created empty lists. (Note thate=f=[] assignsthesame object to bothe andf.)

3.2.The standard type hierarchy

Below is a list of the types that are built into Python. Extension modules(written in C, Java, or other languages, depending on the implementation) candefine additional types. Future versions of Python may add types to the typehierarchy (e.g., rational numbers, efficiently stored arrays of integers, etc.),although such additions will often be provided via the standard library instead.

Some of the type descriptions below contain a paragraph listing ‘specialattributes.’ These are attributes that provide access to the implementation andare not intended for general use. Their definition may change in the future.

3.2.1.None

This type has a single value. There is a single object with this value. Thisobject is accessed through the built-in nameNone. It is used to signify theabsence of a value in many situations, e.g., it is returned from functions thatdon’t explicitly return anything. Its truth value is false.

3.2.2.NotImplemented

This type has a single value. There is a single object with this value. Thisobject is accessed through the built-in nameNotImplemented. Numeric methodsand rich comparison methods should return this value if they do not implement theoperation for the operands provided. (The interpreter will then try thereflected operation, or some other fallback, depending on the operator.) Itshould not be evaluated in a boolean context.

SeeImplementing the arithmetic operationsfor more details.

Changed in version 3.9:EvaluatingNotImplemented in a boolean context is deprecated. Whileit currently evaluates as true, it will emit aDeprecationWarning.It will raise aTypeError in a future version of Python.

3.2.3.Ellipsis

This type has a single value. There is a single object with this value. Thisobject is accessed through the literal... or the built-in nameEllipsis. Its truth value is true.

3.2.4.numbers.Number

These are created by numeric literals and returned as results by arithmeticoperators and arithmetic built-in functions. Numeric objects are immutable;once created their value never changes. Python numbers are of course stronglyrelated to mathematical numbers, but subject to the limitations of numericalrepresentation in computers.

The string representations of the numeric classes, computed by__repr__() and__str__(), have the followingproperties:

  • They are valid numeric literals which, when passed to theirclass constructor, produce an object having the value of theoriginal numeric.

  • The representation is in base 10, when possible.

  • Leading zeros, possibly excepting a single zero before adecimal point, are not shown.

  • Trailing zeros, possibly excepting a single zero after adecimal point, are not shown.

  • A sign is shown only when the number is negative.

Python distinguishes between integers, floating-point numbers, and complexnumbers:

3.2.4.1.numbers.Integral

These represent elements from the mathematical set of integers (positive andnegative).

Note

The rules for integer representation are intended to give the most meaningfulinterpretation of shift and mask operations involving negative integers.

There are two types of integers:

Integers (int)

These represent numbers in an unlimited range, subject to available (virtual)memory only. For the purpose of shift and mask operations, a binaryrepresentation is assumed, and negative numbers are represented in a variant of2’s complement which gives the illusion of an infinite string of sign bitsextending to the left.

Booleans (bool)

These represent the truth values False and True. The two objects representingthe valuesFalse andTrue are the only Boolean objects. The Boolean type is asubtype of the integer type, and Boolean values behave like the values 0 and 1,respectively, in almost all contexts, the exception being that when converted toa string, the strings"False" or"True" are returned, respectively.

3.2.4.2.numbers.Real (float)

These represent machine-level double precision floating-point numbers. You areat the mercy of the underlying machine architecture (and C or Javaimplementation) for the accepted range and handling of overflow. Python does notsupport single-precision floating-point numbers; the savings in processor andmemory usage that are usually the reason for using these are dwarfed by theoverhead of using objects in Python, so there is no reason to complicate thelanguage with two kinds of floating-point numbers.

3.2.4.3.numbers.Complex (complex)

These represent complex numbers as a pair of machine-level double precisionfloating-point numbers. The same caveats apply as for floating-point numbers.The real and imaginary parts of a complex numberz can be retrieved throughthe read-only attributesz.real andz.imag.

3.2.5.Sequences

These represent finite ordered sets indexed by non-negative numbers. Thebuilt-in functionlen() returns the number of items of a sequence. Whenthe length of a sequence isn, the index set contains the numbers 0, 1,…,n-1. Itemi of sequencea is selected bya[i]. Some sequences,including built-in sequences, interpret negative subscripts by adding thesequence length. For example,a[-2] equalsa[n-2], the second to lastitem of sequence a with lengthn.

Sequences also support slicing:a[i:j] selects all items with indexk suchthati<=k<j. When used as an expression, a slice is asequence of the same type. The comment above about negative indexes also appliesto negative slice positions.

Some sequences also support “extended slicing” with a third “step” parameter:a[i:j:k] selects all items ofa with indexx wherex=i+n*k,n>=0 andi<=x<j.

Sequences are distinguished according to their mutability:

3.2.5.1.Immutable sequences

An object of an immutable sequence type cannot change once it is created. (Ifthe object contains references to other objects, these other objects may bemutable and may be changed; however, the collection of objects directlyreferenced by an immutable object cannot change.)

The following types are immutable sequences:

Strings

A string is a sequence of values that represent Unicode code points.All the code points in the rangeU+0000-U+10FFFF can berepresented in a string. Python doesn’t have achar type;instead, every code point in the string is represented as a stringobject with length1. The built-in functionord()converts a code point from its string form to an integer in therange0-10FFFF;chr() converts an integer in the range0-10FFFF to the corresponding length1 string object.str.encode() can be used to convert astr tobytes using the given text encoding, andbytes.decode() can be used to achieve the opposite.

Tuples

The items of a tuple are arbitrary Python objects. Tuples of two ormore items are formed by comma-separated lists of expressions. A tupleof one item (a ‘singleton’) can be formed by affixing a comma to anexpression (an expression by itself does not create a tuple, sinceparentheses must be usable for grouping of expressions). An emptytuple can be formed by an empty pair of parentheses.

Bytes

A bytes object is an immutable array. The items are 8-bit bytes,represented by integers in the range 0 <= x < 256. Bytes literals(likeb'abc') and the built-inbytes() constructorcan be used to create bytes objects. Also, bytes objects can bedecoded to strings via thedecode() method.

3.2.5.2.Mutable sequences

Mutable sequences can be changed after they are created. The subscription andslicing notations can be used as the target of assignment anddel(delete) statements.

Note

Thecollections andarray module provideadditional examples of mutable sequence types.

There are currently two intrinsic mutable sequence types:

Lists

The items of a list are arbitrary Python objects. Lists are formed byplacing a comma-separated list of expressions in square brackets. (Notethat there are no special cases needed to form lists of length 0 or 1.)

Byte Arrays

A bytearray object is a mutable array. They are created by the built-inbytearray() constructor. Aside from being mutable(and hence unhashable), byte arrays otherwise provide the same interfaceand functionality as immutablebytes objects.

3.2.6.Set types

These represent unordered, finite sets of unique, immutable objects. As such,they cannot be indexed by any subscript. However, they can be iterated over, andthe built-in functionlen() returns the number of items in a set. Commonuses for sets are fast membership testing, removing duplicates from a sequence,and computing mathematical operations such as intersection, union, difference,and symmetric difference.

For set elements, the same immutability rules apply as for dictionary keys. Notethat numeric types obey the normal rules for numeric comparison: if two numberscompare equal (e.g.,1 and1.0), only one of them can be contained in aset.

There are currently two intrinsic set types:

Sets

These represent a mutable set. They are created by the built-inset()constructor and can be modified afterwards by several methods, such asadd().

Frozen sets

These represent an immutable set. They are created by the built-infrozenset() constructor. As a frozenset is immutable andhashable, it can be used again as an element of another set, or asa dictionary key.

3.2.7.Mappings

These represent finite sets of objects indexed by arbitrary index sets. Thesubscript notationa[k] selects the item indexed byk from the mappinga; this can be used in expressions and as the target of assignments ordel statements. The built-in functionlen() returns the numberof items in a mapping.

There is currently a single intrinsic mapping type:

3.2.7.1.Dictionaries

These represent finite sets of objects indexed by nearly arbitrary values. Theonly types of values not acceptable as keys are values containing lists ordictionaries or other mutable types that are compared by value rather than byobject identity, the reason being that the efficient implementation ofdictionaries requires a key’s hash value to remain constant. Numeric types usedfor keys obey the normal rules for numeric comparison: if two numbers compareequal (e.g.,1 and1.0) then they can be used interchangeably to indexthe same dictionary entry.

Dictionaries preserve insertion order, meaning that keys will be producedin the same order they were added sequentially over the dictionary.Replacing an existing key does not change the order, however removing a keyand re-inserting it will add it to the end instead of keeping its old place.

Dictionaries are mutable; they can be created by the{} notation (seesectionDictionary displays).

The extension modulesdbm.ndbm anddbm.gnu provideadditional examples of mapping types, as does thecollectionsmodule.

Changed in version 3.7:Dictionaries did not preserve insertion order in versions of Python before 3.6.In CPython 3.6, insertion order was preserved, but it was consideredan implementation detail at that time rather than a language guarantee.

3.2.8.Callable types

These are the types to which the function call operation (see sectionCalls) can be applied:

3.2.8.1.User-defined functions

A user-defined function object is created by a function definition (seesectionFunction definitions). It should be called with an argument listcontaining the same number of items as the function’s formal parameterlist.

3.2.8.1.1.Special read-only attributes

Attribute

Meaning

function.__globals__

A reference to thedictionary that holds the function’sglobal variables – the global namespace of the modulein which the function was defined.

function.__closure__

None or atuple of cells that contain bindings for the names specifiedin theco_freevars attribute of the function’scodeobject.

A cell object has the attributecell_contents.This can be used to get the value of the cell, as well as set the value.

3.2.8.1.2.Special writable attributes

Most of these attributes check the type of the assigned value:

Attribute

Meaning

function.__doc__

The function’s documentation string, orNone if unavailable.

function.__name__

The function’s name.See also:__name__attributes.

function.__qualname__

The function’squalified name.See also:__qualname__attributes.

Added in version 3.3.

function.__module__

The name of the module the function was defined in,orNone if unavailable.

function.__defaults__

Atuple containing defaultparameter valuesfor those parameters that have defaults,orNone if no parameters have a default value.

function.__code__

Thecode object representingthe compiled function body.

function.__dict__

The namespace supporting arbitrary function attributes.See also:__dict__attributes.

function.__annotations__

Adictionary containing annotations ofparameters.The keys of the dictionary are the parameter names,and'return' for the return annotation, if provided.See also:Annotations Best Practices.

function.__kwdefaults__

Adictionary containing defaults for keyword-onlyparameters.

function.__type_params__

Atuple containing thetype parameters ofageneric function.

Added in version 3.12.

Function objects also support getting and setting arbitrary attributes, whichcan be used, for example, to attach metadata to functions. Regular attributedot-notation is used to get and set such attributes.

CPython implementation detail: CPython’s current implementation only supports function attributeson user-defined functions. Function attributes onbuilt-in functions may be supported in thefuture.

Additional information about a function’s definition can be retrieved from itscode object(accessible via the__code__ attribute).

3.2.8.2.Instance methods

An instance method object combines a class, a class instance and anycallable object (normally a user-defined function).

Special read-only attributes:

method.__self__

Refers to the class instance object to which the method isbound

method.__func__

Refers to the originalfunction object

method.__doc__

The method’s documentation(same asmethod.__func__.__doc__).Astring if the original function had a docstring, elseNone.

method.__name__

The name of the method(same asmethod.__func__.__name__)

method.__module__

The name of the module the method was defined in, orNone ifunavailable.

Methods also support accessing (but not setting) the arbitrary functionattributes on the underlyingfunction object.

User-defined method objects may be created when getting an attribute of aclass (perhaps via an instance of that class), if that attribute is auser-definedfunction object or aclassmethod object.

When an instance method object is created by retrieving a user-definedfunction object from a class via one of itsinstances, its__self__ attribute is the instance, and themethod object is said to bebound. The new method’s__func__attribute is the original function object.

When an instance method object is created by retrieving aclassmethodobject from a class or instance, its__self__ attribute is theclass itself, and its__func__ attribute is the function objectunderlying the class method.

When an instance method object is called, the underlying function(__func__) is called, inserting the class instance(__self__) in front of the argument list. For instance, whenC is a class which contains a definition for a functionf(), andx is an instance ofC, callingx.f(1) isequivalent to callingC.f(x,1).

When an instance method object is derived from aclassmethod object, the“class instance” stored in__self__ will actually be the classitself, so that calling eitherx.f(1) orC.f(1) is equivalent tocallingf(C,1) wheref is the underlying function.

It is important to note that user-defined functionswhich are attributes of a class instance are not converted to boundmethods; thisonly happens when the function is an attribute of theclass.

3.2.8.3.Generator functions

A function or method which uses theyield statement (see sectionThe yield statement) is called agenerator function. Such a function, whencalled, always returns aniterator object which can be used toexecute the body of the function: calling the iterator’siterator.__next__() method will cause the function to execute untilit provides a value using theyield statement. When thefunction executes areturn statement or falls off the end, aStopIteration exception is raised and the iterator will havereached the end of the set of values to be returned.

3.2.8.4.Coroutine functions

A function or method which is defined usingasyncdef is calledacoroutine function. Such a function, when called, returns acoroutine object. It may containawait expressions,as well asasyncwith andasyncfor statements. Seealso theCoroutine Objects section.

3.2.8.5.Asynchronous generator functions

A function or method which is defined usingasyncdef andwhich uses theyield statement is called aasynchronous generator function. Such a function, when called,returns anasynchronous iterator object which can be used in anasyncfor statement to execute the body of the function.

Calling the asynchronous iterator’saiterator.__anext__ methodwill return anawaitable which when awaitedwill execute until it provides a value using theyieldexpression. When the function executes an emptyreturnstatement or falls off the end, aStopAsyncIteration exceptionis raised and the asynchronous iterator will have reached the end ofthe set of values to be yielded.

3.2.8.6.Built-in functions

A built-in function object is a wrapper around a C function. Examples ofbuilt-in functions arelen() andmath.sin() (math is astandard built-in module). The number and type of the arguments aredetermined by the C function. Special read-only attributes:

  • __doc__ is the function’s documentation string, orNone ifunavailable. Seefunction.__doc__.

  • __name__ is the function’s name. Seefunction.__name__.

  • __self__ is set toNone (but see the next item).

  • __module__ is the name ofthe module the function was defined in orNone if unavailable.Seefunction.__module__.

3.2.8.7.Built-in methods

This is really a different disguise of a built-in function, this time containingan object passed to the C function as an implicit extra argument. An example ofa built-in method isalist.append(), assumingalist is a list object. Inthis case, the special read-only attribute__self__ is set to the objectdenoted byalist. (The attribute has the same semantics as it does withotherinstancemethods.)

3.2.8.8.Classes

Classes are callable. These objects normally act as factories for newinstances of themselves, but variations are possible for class types thatoverride__new__(). The arguments of the call are passed to__new__() and, in the typical case, to__init__() toinitialize the new instance.

3.2.8.9.Class Instances

Instances of arbitrary classes can be made callable by defining a__call__() method in their class.

3.2.9.Modules

Modules are a basic organizational unit of Python code, and are created bytheimport system as invoked either by theimport statement, or by callingfunctions such asimportlib.import_module() and built-in__import__(). A module object has a namespace implemented by adictionary object (this is the dictionary referenced by the__globals__attribute of functions defined in the module). Attribute references aretranslated to lookups in this dictionary, e.g.,m.x is equivalent tom.__dict__["x"]. A module object does not contain the code object usedto initialize the module (since it isn’t needed once the initialization isdone).

Attribute assignment updates the module’s namespace dictionary, e.g.,m.x=1 is equivalent tom.__dict__["x"]=1.

3.2.9.1.Import-related attributes on module objects

Module objects have the following attributes that relate to theimport system. When a module is created using the machinery associatedwith the import system, these attributes are filled in based on the module’sspec, before theloader executes and loads themodule.

To create a module dynamically rather than using the import system,it’s recommended to useimportlib.util.module_from_spec(),which will set the various import-controlled attributes to appropriate values.It’s also possible to use thetypes.ModuleType constructor to createmodules directly, but this technique is more error-prone, as most attributesmust be manually set on the module object after it has been created when usingthis approach.

Caution

With the exception of__name__, it isstronglyrecommended that you rely on__spec__ and its attributesinstead of any of the other individual attributes listed in this subsection.Note that updating an attribute on__spec__ will not update thecorresponding attribute on the module itself:

>>>importtyping>>>typing.__name__,typing.__spec__.name('typing', 'typing')>>>typing.__spec__.name='spelling'>>>typing.__name__,typing.__spec__.name('typing', 'spelling')>>>typing.__name__='keyboard_smashing'>>>typing.__name__,typing.__spec__.name('keyboard_smashing', 'spelling')
module.__name__

The name used to uniquely identify the module in the import system.For a directly executed module, this will be set to"__main__".

This attribute must be set to the fully qualified name of the module.It is expected to match the value ofmodule.__spec__.name.

module.__spec__

A record of the module’s import-system-related state.

Set to themodulespec that wasused when importing the module. SeeModule specs for more details.

Added in version 3.4.

module.__package__

Thepackage a module belongs to.

If the module is top-level (that is, not a part of any specific package)then the attribute should be set to'' (the empty string). Otherwise,it should be set to the name of the module’s package (which can be equal tomodule.__name__ if the module itself is a package). SeePEP 366for further details.

This attribute is used instead of__name__ to calculateexplicit relative imports for main modules. It defaults toNone formodules created dynamically using thetypes.ModuleType constructor;useimportlib.util.module_from_spec() instead to ensure the attributeis set to astr.

It isstrongly recommended that you usemodule.__spec__.parentinstead ofmodule.__package__.__package__ is now only usedas a fallback if__spec__.parent is not set, and this fallbackpath is deprecated.

Changed in version 3.4:This attribute now defaults toNone for modules created dynamicallyusing thetypes.ModuleType constructor.Previously the attribute was optional.

Changed in version 3.6:The value of__package__ is expected to be the same as__spec__.parent.__package__ is now only used as a fallback during importresolution if__spec__.parent is not defined.

Changed in version 3.10:ImportWarning is raised if an import resolution falls back to__package__ instead of__spec__.parent.

Changed in version 3.12:RaiseDeprecationWarning instead ofImportWarning whenfalling back to__package__ during import resolution.

Deprecated since version 3.13, will be removed in version 3.15:__package__ will cease to be set or taken into considerationby the import system or standard library.

module.__loader__

Theloader object that the import machinery used to load the module.

This attribute is mostly useful for introspection, but can be used foradditional loader-specific functionality, for example getting dataassociated with a loader.

__loader__ defaults toNone for modules created dynamicallyusing thetypes.ModuleType constructor;useimportlib.util.module_from_spec() instead to ensure the attributeis set to aloader object.

It isstrongly recommended that you usemodule.__spec__.loaderinstead ofmodule.__loader__.

Changed in version 3.4:This attribute now defaults toNone for modules created dynamicallyusing thetypes.ModuleType constructor.Previously the attribute was optional.

Deprecated since version 3.12, will be removed in version 3.16:Setting__loader__ on a module while failing to set__spec__.loader is deprecated. In Python 3.16,__loader__ will cease to be set or taken into consideration bythe import system or the standard library.

module.__path__

A (possibly empty)sequence of strings enumerating the locationswhere the package’s submodules will be found. Non-package modules shouldnot have a__path__ attribute. See__path__ attributes on modules formore details.

It isstrongly recommended that you usemodule.__spec__.submodule_search_locationsinstead ofmodule.__path__.

module.__file__
module.__cached__

__file__ and__cached__ are both optional attributes thatmay or may not be set. Both attributes should be astr when theyare available.

__file__ indicates the pathname of the file from which the modulewas loaded (if loaded from a file), or the pathname of the shared libraryfile for extension modules loaded dynamically from a shared library.It might be missing for certain types of modules, such as C modules that arestatically linked into the interpreter, and theimport system may opt to leave it unset if ithas no semantic meaning (for example, a module loaded from a database).

If__file__ is set then the__cached__ attribute mightalso be set, which is the path to any compiled version ofthe code (for example, a byte-compiled file). The file does not need to existto set this attribute; the path can simply point to where thecompiled filewould exist (seePEP 3147).

Note that__cached__ may be set even if__file__ is notset. However, that scenario is quite atypical. Ultimately, theloader is what makes use of the module spec provided by thefinder (from which__file__ and__cached__ arederived). So if a loader can load from a cached module but otherwise doesnot load from a file, that atypical scenario may be appropriate.

It isstrongly recommended that you usemodule.__spec__.cachedinstead ofmodule.__cached__.

Deprecated since version 3.13, will be removed in version 3.15:Setting__cached__ on a module while failing to set__spec__.cached is deprecated. In Python 3.15,__cached__ will cease to be set or taken into consideration bythe import system or standard library.

3.2.9.2.Other writable attributes on module objects

As well as the import-related attributes listed above, module objects also havethe following writable attributes:

module.__doc__

The module’s documentation string, orNone if unavailable.See also:__doc__attributes.

module.__annotations__

A dictionary containingvariable annotations collected during modulebody execution. For best practices on working with__annotations__,please seeAnnotations Best Practices.

3.2.9.3.Module dictionaries

Module objects also have the following special read-only attribute:

module.__dict__

The module’s namespace as a dictionary object. Uniquely among the attributeslisted here,__dict__ cannot be accessed as a global variable fromwithin a module; it can only be accessed as an attribute on module objects.

CPython implementation detail: Because of the way CPython clears module dictionaries, the moduledictionary will be cleared when the module falls out of scope even if thedictionary still has live references. To avoid this, copy the dictionaryor keep the module around while using its dictionary directly.

3.2.10.Custom classes

Custom class types are typically created by class definitions (see sectionClass definitions). A class has a namespace implemented by a dictionary object.Class attribute references are translated to lookups in this dictionary, e.g.,C.x is translated toC.__dict__["x"] (although there are a number ofhooks which allow for other means of locating attributes). When the attributename is not found there, the attribute search continues in the base classes.This search of the base classes uses the C3 method resolution order whichbehaves correctly even in the presence of ‘diamond’ inheritance structureswhere there are multiple inheritance paths leading back to a common ancestor.Additional details on the C3 MRO used by Python can be found atThe Python 2.3 Method Resolution Order.

When a class attribute reference (for classC, say) would yield aclass method object, it is transformed into an instance method object whose__self__ attribute isC.When it would yield astaticmethod object,it is transformed into the object wrapped by the static methodobject. See sectionImplementing Descriptors for another way in which attributesretrieved from a class may differ from those actually contained in its__dict__.

Class attribute assignments update the class’s dictionary, never the dictionaryof a base class.

A class object can be called (see above) to yield a class instance (see below).

3.2.10.1.Special attributes

Attribute

Meaning

type.__name__

The class’s name.See also:__name__attributes.

type.__qualname__

The class’squalified name.See also:__qualname__attributes.

type.__module__

The name of the module in which the class was defined.

type.__dict__

Amappingproxyproviding a read-only view of the class’s namespace.See also:__dict__attributes.

type.__bases__

Atuple containing the class’s bases.In most cases, for a class defined asclassX(A,B,C),X.__bases__ will be exactly equal to(A,B,C).

type.__doc__

The class’s documentation string, orNone if undefined.Not inherited by subclasses.

type.__annotations__

A dictionary containingvariable annotationscollected during class body execution. For best practices on workingwith__annotations__, please seeAnnotations Best Practices.

Caution

Accessing the__annotations__ attribute of a classobject directly may yield incorrect results in the presence ofmetaclasses. In addition, the attribute may not exist forsome classes. Useinspect.get_annotations() toretrieve class annotations safely.

type.__type_params__

Atuple containing thetype parameters ofageneric class.

Added in version 3.12.

type.__static_attributes__

Atuple containing names of attributes of this class which areassigned throughself.X from any function in its body.

Added in version 3.13.

type.__firstlineno__

The line number of the first line of the class definition,including decorators.Setting the__module__ attribute removes the__firstlineno__ item from the type’s dictionary.

Added in version 3.13.

type.__mro__

Thetuple of classes that are considered when looking forbase classes during method resolution.

3.2.10.2.Special methods

In addition to the special attributes described above, all Python classes alsohave the following two methods available:

type.mro()

This method can be overridden by a metaclass to customize the methodresolution order for its instances. It is called at class instantiation,and its result is stored in__mro__.

type.__subclasses__()

Each class keeps a list of weak references to its immediate subclasses. Thismethod returns a list of all those references still alive. The list is indefinition order. Example:

>>>classA:pass>>>classB(A):pass>>>A.__subclasses__()[<class 'B'>]

3.2.11.Class instances

A class instance is created by calling a class object (see above). A classinstance has a namespace implemented as a dictionary which is the first placein which attribute references are searched. When an attribute is not foundthere, and the instance’s class has an attribute by that name, the searchcontinues with the class attributes. If a class attribute is found that is auser-defined function object, it is transformed into an instance methodobject whose__self__ attribute is the instance. Static method andclass method objects are also transformed; see above under “Classes”. SeesectionImplementing Descriptors for another way in which attributes of a classretrieved via its instances may differ from the objects actually stored inthe class’s__dict__. If no class attribute is found, and theobject’s class has a__getattr__() method, that is called to satisfythe lookup.

Attribute assignments and deletions update the instance’s dictionary, never aclass’s dictionary. If the class has a__setattr__() or__delattr__() method, this is called instead of updating the instancedictionary directly.

Class instances can pretend to be numbers, sequences, or mappings if they havemethods with certain special names. See sectionSpecial method names.

3.2.11.1.Special attributes

object.__class__

The class to which a class instance belongs.

object.__dict__

A dictionary or other mapping object used to store an object’s (writable)attributes. Not all instances have a__dict__ attribute; see thesection on__slots__ for more details.

3.2.12.I/O objects (also known as file objects)

Afile object represents an open file. Various shortcuts areavailable to create file objects: theopen() built-in function, andalsoos.popen(),os.fdopen(), and themakefile() method of socket objects (and perhaps byother functions or methods provided by extension modules).

The objectssys.stdin,sys.stdout andsys.stderr areinitialized to file objects corresponding to the interpreter’s standardinput, output and error streams; they are all open in text mode andtherefore follow the interface defined by theio.TextIOBaseabstract class.

3.2.13.Internal types

A few types used internally by the interpreter are exposed to the user. Theirdefinitions may change with future versions of the interpreter, but they arementioned here for completeness.

3.2.13.1.Code objects

Code objects representbyte-compiled executable Python code, orbytecode.The difference between a code object and a function object is that the functionobject contains an explicit reference to the function’s globals (the module inwhich it was defined), while a code object contains no context; also the defaultargument values are stored in the function object, not in the code object(because they represent values calculated at run-time). Unlike functionobjects, code objects are immutable and contain no references (directly orindirectly) to mutable objects.

3.2.13.1.1.Special read-only attributes
codeobject.co_name

The function name

codeobject.co_qualname

The fully qualified function name

Added in version 3.11.

codeobject.co_argcount

The total number of positionalparameters(including positional-only parameters and parameters with default values)that the function has

codeobject.co_posonlyargcount

The number of positional-onlyparameters(including arguments with default values) that the function has

codeobject.co_kwonlyargcount

The number of keyword-onlyparameters(including arguments with default values) that the function has

codeobject.co_nlocals

The number oflocal variables used by the function(including parameters)

codeobject.co_varnames

Atuple containing the names of the local variables in thefunction (starting with the parameter names)

codeobject.co_cellvars

Atuple containing the names oflocal variablesthat are referenced from at least onenested scope inside the function

codeobject.co_freevars

Atuple containing the names offree (closure) variables that anested scopereferences in an outer scope. See alsofunction.__closure__.

Note: references to global and builtin names arenot included.

codeobject.co_code

A string representing the sequence ofbytecode instructions inthe function

codeobject.co_consts

Atuple containing the literals used by thebytecode inthe function

codeobject.co_names

Atuple containing the names used by thebytecode inthe function

codeobject.co_filename

The name of the file from which the code was compiled

codeobject.co_firstlineno

The line number of the first line of the function

codeobject.co_lnotab

A string encoding the mapping frombytecode offsets to linenumbers. For details, see the source code of the interpreter.

Deprecated since version 3.12:This attribute of code objects is deprecated, and may be removed inPython 3.15.

codeobject.co_stacksize

The required stack size of the code object

codeobject.co_flags

Aninteger encoding a number of flags for theinterpreter.

The following flag bits are defined forco_flags:bit0x04 is set ifthe function uses the*arguments syntax to accept an arbitrary number ofpositional arguments; bit0x08 is set if the function uses the**keywords syntax to accept arbitrary keyword arguments; bit0x20 is setif the function is a generator. SeeCode Objects Bit Flags for detailson the semantics of each flags that might be present.

Future feature declarations (for example,from__future__importdivision) also use bitsinco_flags to indicate whether a code object was compiled with aparticular feature enabled. Seecompiler_flag.

Other bits inco_flags are reserved for internal use.

If a code object represents a function, the first item inco_consts isthe documentation string of the function, orNone if undefined.

3.2.13.1.2.Methods on code objects
codeobject.co_positions()

Returns an iterable over the source code positions of eachbytecodeinstruction in the code object.

The iterator returnstuples containing the(start_line,end_line,start_column,end_column). Thei-th tuple corresponds to theposition of the source code that compiled to thei-th code unit.Column information is 0-indexed utf-8 byte offsets on the given sourceline.

This positional information can be missing. A non-exhaustive lists ofcases where this may happen:

  • Running the interpreter with-Xno_debug_ranges.

  • Loading a pyc file compiled while using-Xno_debug_ranges.

  • Position tuples corresponding to artificial instructions.

  • Line and column numbers that can’t be represented due toimplementation specific limitations.

When this occurs, some or all of the tuple elements can beNone.

Added in version 3.11.

Note

This feature requires storing column positions in code objects which mayresult in a small increase of disk usage of compiled Python files orinterpreter memory usage. To avoid storing the extra information and/ordeactivate printing the extra traceback information, the-Xno_debug_ranges command line flag or thePYTHONNODEBUGRANGESenvironment variable can be used.

codeobject.co_lines()

Returns an iterator that yields information about successive ranges ofbytecodes. Each item yielded is a(start,end,lineno)tuple:

  • start (anint) represents the offset (inclusive) of the startof thebytecode range

  • end (anint) represents the offset (exclusive) of the end ofthebytecode range

  • lineno is anint representing the line number of thebytecode range, orNone if the bytecodes in the given rangehave no line number

The items yielded will have the following properties:

  • The first range yielded will have astart of 0.

  • The(start,end) ranges will be non-decreasing and consecutive. Thatis, for any pair oftuples, thestart of the second will beequal to theend of the first.

  • No range will be backwards:end>=start for all triples.

  • The lasttuple yielded will haveend equal to the size of thebytecode.

Zero-width ranges, wherestart==end, are allowed. Zero-width rangesare used for lines that are present in the source code, but have beeneliminated by thebytecode compiler.

Added in version 3.10.

See also

PEP 626 - Precise line numbers for debugging and other tools.

The PEP that introduced theco_lines() method.

codeobject.replace(**kwargs)

Return a copy of the code object with new values for the specified fields.

Code objects are also supported by the generic functioncopy.replace().

Added in version 3.8.

3.2.13.2.Frame objects

Frame objects represent execution frames. They may occur intraceback objects,and are also passed to registered trace functions.

3.2.13.2.1.Special read-only attributes
frame.f_back

Points to the previous stack frame (towards the caller),orNone if this is the bottom stack frame

frame.f_code

Thecode object being executed in this frame.Accessing this attribute raises anauditing eventobject.__getattr__ with argumentsobj and"f_code".

frame.f_locals

The mapping used by the frame to look uplocal variables.If the frame refers to anoptimized scope,this may return a write-through proxy object.

Changed in version 3.13:Return a proxy for optimized scopes.

frame.f_globals

The dictionary used by the frame to look upglobal variables

frame.f_builtins

The dictionary used by the frame to look upbuilt-in (intrinsic) names

frame.f_lasti

The “precise instruction” of the frame object(this is an index into thebytecode string of thecode object)

3.2.13.2.2.Special writable attributes
frame.f_trace

If notNone, this is a function called for various events duringcode execution (this is used by debuggers). Normally an event istriggered for each new source line (seef_trace_lines).

frame.f_trace_lines

Set this attribute toFalse to disable triggering a tracingevent for each source line.

frame.f_trace_opcodes

Set this attribute toTrue to allow per-opcode events to berequested. Note that this may lead toundefined interpreter behaviour if exceptions raised by the tracefunction escape to the function being traced.

frame.f_lineno

The current line number of the frame – writing to thisfrom within a trace function jumps to the given line (only for the bottom-mostframe). A debugger can implement a Jump command (aka Set Next Statement)by writing to this attribute.

3.2.13.2.3.Frame object methods

Frame objects support one method:

frame.clear()

This method clears all references tolocal variables held by theframe. Also, if the frame belonged to agenerator, the generatoris finalized. This helps break reference cycles involving frameobjects (for example when catching anexceptionand storing itstraceback for later use).

RuntimeError is raised if the frame is currently executingor suspended.

Added in version 3.4.

Changed in version 3.13:Attempting to clear a suspended frame raisesRuntimeError(as has always been the case for executing frames).

3.2.13.3.Traceback objects

Traceback objects represent the stack trace of anexception.A traceback objectis implicitly created when an exception occurs, and may also be explicitlycreated by callingtypes.TracebackType.

Changed in version 3.7:Traceback objects can now be explicitly instantiated from Python code.

For implicitly created tracebacks, when the search for an exception handlerunwinds the execution stack, at each unwound level a traceback object isinserted in front of the current traceback. When an exception handler isentered, the stack trace is made available to the program. (See sectionThe try statement.) It is accessible as the third item of thetuple returned bysys.exc_info(), and as the__traceback__ attributeof the caught exception.

When the program contains no suitablehandler, the stack trace is written (nicely formatted) to the standard errorstream; if the interpreter is interactive, it is also made available to the userassys.last_traceback.

For explicitly created tracebacks, it is up to the creator of the tracebackto determine how thetb_next attributes should be linked toform a full stack trace.

Special read-only attributes:

traceback.tb_frame

Points to the executionframe of the currentlevel.

Accessing this attribute raises anauditing eventobject.__getattr__ with argumentsobj and"tb_frame".

traceback.tb_lineno

Gives the line number where the exception occurred

traceback.tb_lasti

Indicates the “precise instruction”.

The line number and last instruction in the traceback may differ from theline number of itsframe object if the exceptionoccurred in atry statement with no matching except clause or with afinally clause.

traceback.tb_next

The special writable attributetb_next is the next level in thestack trace (towards the frame where the exception occurred), orNone ifthere is no next level.

Changed in version 3.7:This attribute is now writable

3.2.13.4.Slice objects

Slice objects are used to represent slices for__getitem__()methods. They are also created by the built-inslice() function.

Special read-only attributes:start is the lower bound;stop is the upper bound;step is the stepvalue; each isNone if omitted. These attributes can have any type.

Slice objects support one method:

slice.indices(self,length)

This method takes a single integer argumentlength and computesinformation about the slice that the slice object would describe ifapplied to a sequence oflength items. It returns a tuple of threeintegers; respectively these are thestart andstop indices and thestep or stride length of the slice. Missing or out-of-bounds indicesare handled in a manner consistent with regular slices.

3.2.13.5.Static method objects

Static method objects provide a way of defeating the transformation of functionobjects to method objects described above. A static method object is a wrapperaround any other object, usually a user-defined method object. When a staticmethod object is retrieved from a class or a class instance, the object actuallyreturned is the wrapped object, which is not subject to any furthertransformation. Static method objects are also callable. Static methodobjects are created by the built-instaticmethod() constructor.

3.2.13.6.Class method objects

A class method object, like a static method object, is a wrapper around anotherobject that alters the way in which that object is retrieved from classes andclass instances. The behaviour of class method objects upon such retrieval isdescribed above, under“instance methods”. Class method objects are createdby the built-inclassmethod() constructor.

3.3.Special method names

A class can implement certain operations that are invoked by special syntax(such as arithmetic operations or subscripting and slicing) by defining methodswith special names. This is Python’s approach tooperator overloading,allowing classes to define their own behavior with respect to languageoperators. For instance, if a class defines a method named__getitem__(),andx is an instance of this class, thenx[i] is roughly equivalenttotype(x).__getitem__(x,i). Except where mentioned, attempts to execute anoperation raise an exception when no appropriate method is defined (typicallyAttributeError orTypeError).

Setting a special method toNone indicates that the correspondingoperation is not available. For example, if a class sets__iter__() toNone, the class is not iterable, so callingiter() on its instances will raise aTypeError (withoutfalling back to__getitem__()).[2]

When implementing a class that emulates any built-in type, it is important thatthe emulation only be implemented to the degree that it makes sense for theobject being modelled. For example, some sequences may work well with retrievalof individual elements, but extracting a slice may not make sense. (One exampleof this is theNodeList interface in the W3C’s DocumentObject Model.)

3.3.1.Basic customization

object.__new__(cls[,...])

Called to create a new instance of classcls.__new__() is a staticmethod (special-cased so you need not declare it as such) that takes the classof which an instance was requested as its first argument. The remainingarguments are those passed to the object constructor expression (the call to theclass). The return value of__new__() should be the new object instance(usually an instance ofcls).

Typical implementations create a new instance of the class by invoking thesuperclass’s__new__() method usingsuper().__new__(cls[,...])with appropriate arguments and then modifying the newly created instanceas necessary before returning it.

If__new__() is invoked during object construction and it returns aninstance ofcls, then the new instance’s__init__() methodwill be invoked like__init__(self[,...]), whereself is the new instanceand the remaining arguments are the same as were passed to the object constructor.

If__new__() does not return an instance ofcls, then the new instance’s__init__() method will not be invoked.

__new__() is intended mainly to allow subclasses of immutable types (likeint, str, or tuple) to customize instance creation. It is also commonlyoverridden in custom metaclasses in order to customize class creation.

object.__init__(self[,...])

Called after the instance has been created (by__new__()), but beforeit is returned to the caller. The arguments are those passed to theclass constructor expression. If a base class has an__init__()method, the derived class’s__init__() method, if any, must explicitlycall it to ensure proper initialization of the base class part of theinstance; for example:super().__init__([args...]).

Because__new__() and__init__() work together in constructingobjects (__new__() to create it, and__init__() to customize it),no non-None value may be returned by__init__(); doing so willcause aTypeError to be raised at runtime.

object.__del__(self)

Called when the instance is about to be destroyed. This is also called afinalizer or (improperly) a destructor. If a base class has a__del__() method, the derived class’s__del__() method,if any, must explicitly call it to ensure proper deletion of the baseclass part of the instance.

It is possible (though not recommended!) for the__del__() methodto postpone destruction of the instance by creating a new reference toit. This is called objectresurrection. It is implementation-dependentwhether__del__() is called a second time when a resurrected objectis about to be destroyed; the currentCPython implementationonly calls it once.

It is not guaranteed that__del__() methods are called for objectsthat still exist when the interpreter exits.weakref.finalize provides a straightforward way to registera cleanup function to be called when an object is garbage collected.

Note

delx doesn’t directly callx.__del__() — the former decrementsthe reference count forx by one, and the latter is only called whenx’s reference count reaches zero.

CPython implementation detail: It is possible for a reference cycle to prevent the reference countof an object from going to zero. In this case, the cycle will belater detected and deleted by thecyclic garbage collector. A common cause of reference cycles is whenan exception has been caught in a local variable. The frame’slocals then reference the exception, which references its owntraceback, which references the locals of all frames caught in thetraceback.

See also

Documentation for thegc module.

Warning

Due to the precarious circumstances under which__del__() methods areinvoked, exceptions that occur during their execution are ignored, and a warningis printed tosys.stderr instead. In particular:

  • __del__() can be invoked when arbitrary code is being executed,including from any arbitrary thread. If__del__() needs to takea lock or invoke any other blocking resource, it may deadlock asthe resource may already be taken by the code that gets interruptedto execute__del__().

  • __del__() can be executed during interpreter shutdown. As aconsequence, the global variables it needs to access (including othermodules) may already have been deleted or set toNone. Pythonguarantees that globals whose name begins with a single underscoreare deleted from their module before other globals are deleted; ifno other references to such globals exist, this may help in assuringthat imported modules are still available at the time when the__del__() method is called.

object.__repr__(self)

Called by therepr() built-in function to compute the “official” stringrepresentation of an object. If at all possible, this should look like avalid Python expression that could be used to recreate an object with thesame value (given an appropriate environment). If this is not possible, astring of the form<...someusefuldescription...> should be returned.The return value must be a string object. If a class defines__repr__()but not__str__(), then__repr__() is also used when an“informal” string representation of instances of that class is required.

This is typically used for debugging, so it is important that the representationis information-rich and unambiguous. A default implementation is provided by theobject class itself.

object.__str__(self)

Called bystr(object), the default__format__() implementation,and the built-in functionprint(), to compute the “informal” or nicelyprintable string representation of an object. The return value must be astr object.

This method differs fromobject.__repr__() in that there is noexpectation that__str__() return a valid Python expression: a moreconvenient or concise representation can be used.

The default implementation defined by the built-in typeobjectcallsobject.__repr__().

object.__bytes__(self)

Called bybytes to compute a byte-string representationof an object. This should return abytes object. Theobjectclass itself does not provide this method.

object.__format__(self,format_spec)

Called by theformat() built-in function,and by extension, evaluation offormatted string literals and thestr.format() method, to produce a “formatted”string representation of an object. Theformat_spec argument isa string that contains a description of the formatting options desired.The interpretation of theformat_spec argument is up to the typeimplementing__format__(), however most classes will eitherdelegate formatting to one of the built-in types, or use a similarformatting option syntax.

SeeFormat Specification Mini-Language for a description of the standard formatting syntax.

The return value must be a string object.

The default implementation by theobject class should be givenan emptyformat_spec string. It delegates to__str__().

Changed in version 3.4:The __format__ method ofobject itself raises aTypeErrorif passed any non-empty string.

Changed in version 3.7:object.__format__(x,'') is now equivalent tostr(x) ratherthanformat(str(x),'').

object.__lt__(self,other)
object.__le__(self,other)
object.__eq__(self,other)
object.__ne__(self,other)
object.__gt__(self,other)
object.__ge__(self,other)

These are the so-called “rich comparison” methods. The correspondence betweenoperator symbols and method names is as follows:x<y callsx.__lt__(y),x<=y callsx.__le__(y),x==y callsx.__eq__(y),x!=y callsx.__ne__(y),x>y callsx.__gt__(y), andx>=y callsx.__ge__(y).

A rich comparison method may return the singletonNotImplemented if it doesnot implement the operation for a given pair of arguments. By convention,False andTrue are returned for a successful comparison. However, thesemethods can return any value, so if the comparison operator is used in a Booleancontext (e.g., in the condition of anif statement), Python will callbool() on the value to determine if the result is true or false.

By default,object implements__eq__() by usingis, returningNotImplemented in the case of a false comparison:TrueifxisyelseNotImplemented. For__ne__(), by default itdelegates to__eq__() and inverts the result unless it isNotImplemented. There are no other implied relationships among thecomparison operators or default implementations; for example, the truth of(x<yorx==y) does not implyx<=y. To automatically generate orderingoperations from a single root operation, seefunctools.total_ordering().

By default, theobject class provides implementations consistentwithValue comparisons: equality compares according toobject identity, and order comparisons raiseTypeError. Each defaultmethod may generate these results directly, but may also returnNotImplemented.

See the paragraph on__hash__() forsome important notes on creatinghashable objects which supportcustom comparison operations and are usable as dictionary keys.

There are no swapped-argument versions of these methods (to be used when theleft argument does not support the operation but the right argument does);rather,__lt__() and__gt__() are each other’s reflection,__le__() and__ge__() are each other’s reflection, and__eq__() and__ne__() are their own reflection.If the operands are of different types, and the right operand’s type isa direct or indirect subclass of the left operand’s type,the reflected method of the right operand has priority, otherwisethe left operand’s method has priority. Virtual subclassing isnot considered.

When no appropriate method returns any value other thanNotImplemented, the== and!= operators will fall back tois andisnot, respectively.

object.__hash__(self)

Called by built-in functionhash() and for operations on members ofhashed collections includingset,frozenset, anddict. The__hash__() method should return an integer. The only requiredproperty is that objects which compare equal have the same hash value; it isadvised to mix together the hash values of the components of the object thatalso play a part in comparison of objects by packing them into a tuple andhashing the tuple. Example:

def__hash__(self):returnhash((self.name,self.nick,self.color))

Note

hash() truncates the value returned from an object’s custom__hash__() method to the size of aPy_ssize_t. This istypically 8 bytes on 64-bit builds and 4 bytes on 32-bit builds. If anobject’s__hash__() must interoperate on builds of different bitsizes, be sure to check the width on all supported builds. An easy wayto do this is withpython-c"importsys;print(sys.hash_info.width)".

If a class does not define an__eq__() method it should not define a__hash__() operation either; if it defines__eq__() but not__hash__(), its instances will not be usable as items in hashablecollections. If a class defines mutable objects and implements an__eq__() method, it should not implement__hash__(), since theimplementation ofhashable collections requires that a key’s hash value isimmutable (if the object’s hash value changes, it will be in the wrong hashbucket).

User-defined classes have__eq__() and__hash__() methodsby default (inherited from theobject class); with them, all objects compareunequal (except with themselves) andx.__hash__() returns an appropriatevalue such thatx==y implies both thatxisy andhash(x)==hash(y).

A class that overrides__eq__() and does not define__hash__()will have its__hash__() implicitly set toNone. When the__hash__() method of a class isNone, instances of the class willraise an appropriateTypeError when a program attempts to retrievetheir hash value, and will also be correctly identified as unhashable whencheckingisinstance(obj,collections.abc.Hashable).

If a class that overrides__eq__() needs to retain the implementationof__hash__() from a parent class, the interpreter must be told thisexplicitly by setting__hash__=<ParentClass>.__hash__.

If a class that does not override__eq__() wishes to suppress hashsupport, it should include__hash__=None in the class definition.A class which defines its own__hash__() that explicitly raisesaTypeError would be incorrectly identified as hashable byanisinstance(obj,collections.abc.Hashable) call.

Note

By default, the__hash__() values of str and bytes objects are“salted” with an unpredictable random value. Although theyremain constant within an individual Python process, they are notpredictable between repeated invocations of Python.

This is intended to provide protection against a denial-of-service causedby carefully chosen inputs that exploit the worst case performance of adict insertion,O(n2) complexity. Seehttp://ocert.org/advisories/ocert-2011-003.html for details.

Changing hash values affects the iteration order of sets.Python has never made guarantees about this ordering(and it typically varies between 32-bit and 64-bit builds).

See alsoPYTHONHASHSEED.

Changed in version 3.3:Hash randomization is enabled by default.

object.__bool__(self)

Called to implement truth value testing and the built-in operationbool(); should returnFalse orTrue. When this method is notdefined,__len__() is called, if it is defined, and the object isconsidered true if its result is nonzero. If a class defines neither__len__() nor__bool__() (which is true of theobjectclass itself), all its instances are considered true.

3.3.2.Customizing attribute access

The following methods can be defined to customize the meaning of attributeaccess (use of, assignment to, or deletion ofx.name) for class instances.

object.__getattr__(self,name)

Called when the default attribute access fails with anAttributeError(either__getattribute__() raises anAttributeError becausename is not an instance attribute or an attribute in the class treeforself; or__get__() of aname property raisesAttributeError). This method should either return the (computed)attribute value or raise anAttributeError exception.Theobject class itself does not provide this method.

Note that if the attribute is found through the normal mechanism,__getattr__() is not called. (This is an intentional asymmetry between__getattr__() and__setattr__().) This is done both for efficiencyreasons and because otherwise__getattr__() would have no way to accessother attributes of the instance. Note that at least for instance variables,you can take total control by not inserting any values in the instance attributedictionary (but instead inserting them in another object). See the__getattribute__() method below for a way to actually get total controlover attribute access.

object.__getattribute__(self,name)

Called unconditionally to implement attribute accesses for instances of theclass. If the class also defines__getattr__(), the latter will not becalled unless__getattribute__() either calls it explicitly or raises anAttributeError. This method should return the (computed) attribute valueor raise anAttributeError exception. In order to avoid infiniterecursion in this method, its implementation should always call the base classmethod with the same name to access any attributes it needs, for example,object.__getattribute__(self,name).

Note

This method may still be bypassed when looking up special methods as theresult of implicit invocation via language syntax orbuilt-in functions.SeeSpecial method lookup.

For certain sensitive attribute accesses, raises anauditing eventobject.__getattr__ with argumentsobj andname.

object.__setattr__(self,name,value)

Called when an attribute assignment is attempted. This is called instead ofthe normal mechanism (i.e. store the value in the instance dictionary).name is the attribute name,value is the value to be assigned to it.

If__setattr__() wants to assign to an instance attribute, it shouldcall the base class method with the same name, for example,object.__setattr__(self,name,value).

For certain sensitive attribute assignments, raises anauditing eventobject.__setattr__ with argumentsobj,name,value.

object.__delattr__(self,name)

Like__setattr__() but for attribute deletion instead of assignment. Thisshould only be implemented ifdelobj.name is meaningful for the object.

For certain sensitive attribute deletions, raises anauditing eventobject.__delattr__ with argumentsobj andname.

object.__dir__(self)

Called whendir() is called on the object. An iterable must bereturned.dir() converts the returned iterable to a list and sorts it.

3.3.2.1.Customizing module attribute access

Special names__getattr__ and__dir__ can be also used to customizeaccess to module attributes. The__getattr__ function at the module levelshould accept one argument which is the name of an attribute and return thecomputed value or raise anAttributeError. If an attribute isnot found on a module object through the normal lookup, i.e.object.__getattribute__(), then__getattr__ is searched inthe module__dict__ before raising anAttributeError. If found,it is called with the attribute name and the result is returned.

The__dir__ function should accept no arguments, and return an iterable ofstrings that represents the names accessible on module. If present, thisfunction overrides the standarddir() search on a module.

For a more fine grained customization of the module behavior (settingattributes, properties, etc.), one can set the__class__ attribute ofa module object to a subclass oftypes.ModuleType. For example:

importsysfromtypesimportModuleTypeclassVerboseModule(ModuleType):def__repr__(self):returnf'Verbose{self.__name__}'def__setattr__(self,attr,value):print(f'Setting{attr}...')super().__setattr__(attr,value)sys.modules[__name__].__class__=VerboseModule

Note

Defining module__getattr__ and setting module__class__ onlyaffect lookups made using the attribute access syntax – directly accessingthe module globals (whether by code within the module, or via a referenceto the module’s globals dictionary) is unaffected.

Changed in version 3.5:__class__ module attribute is now writable.

Added in version 3.7:__getattr__ and__dir__ module attributes.

See also

PEP 562 - Module __getattr__ and __dir__

Describes the__getattr__ and__dir__ functions on modules.

3.3.2.2.Implementing Descriptors

The following methods only apply when an instance of the class containing themethod (a so-calleddescriptor class) appears in anowner class (thedescriptor must be in either the owner’s class dictionary or in the classdictionary for one of its parents). In the examples below, “the attribute”refers to the attribute whose name is the key of the property in the ownerclass’__dict__. Theobject class itself does notimplement any of these protocols.

object.__get__(self,instance,owner=None)

Called to get the attribute of the owner class (class attribute access) orof an instance of that class (instance attribute access). The optionalowner argument is the owner class, whileinstance is the instance thatthe attribute was accessed through, orNone when the attribute isaccessed through theowner.

This method should return the computed attribute value or raise anAttributeError exception.

PEP 252 specifies that__get__() is callable with one or twoarguments. Python’s own built-in descriptors support this specification;however, it is likely that some third-party tools have descriptorsthat require both arguments. Python’s own__getattribute__()implementation always passes in both arguments whether they are requiredor not.

object.__set__(self,instance,value)

Called to set the attribute on an instanceinstance of the owner class to anew value,value.

Note, adding__set__() or__delete__() changes the kind ofdescriptor to a “data descriptor”. SeeInvoking Descriptors formore details.

object.__delete__(self,instance)

Called to delete the attribute on an instanceinstance of the owner class.

Instances of descriptors may also have the__objclass__ attributepresent:

object.__objclass__

The attribute__objclass__ is interpreted by theinspect moduleas specifying the class where this object was defined (setting thisappropriately can assist in runtime introspection of dynamic class attributes).For callables, it may indicate that an instance of the given type (or asubclass) is expected or required as the first positional argument (for example,CPython sets this attribute for unbound methods that are implemented in C).

3.3.2.3.Invoking Descriptors

In general, a descriptor is an object attribute with “binding behavior”, onewhose attribute access has been overridden by methods in the descriptorprotocol:__get__(),__set__(), and__delete__(). If any ofthose methods are defined for an object, it is said to be a descriptor.

The default behavior for attribute access is to get, set, or delete theattribute from an object’s dictionary. For instance,a.x has a lookup chainstarting witha.__dict__['x'], thentype(a).__dict__['x'], andcontinuing through the base classes oftype(a) excluding metaclasses.

However, if the looked-up value is an object defining one of the descriptormethods, then Python may override the default behavior and invoke the descriptormethod instead. Where this occurs in the precedence chain depends on whichdescriptor methods were defined and how they were called.

The starting point for descriptor invocation is a binding,a.x. How thearguments are assembled depends ona:

Direct Call

The simplest and least common call is when user code directly invokes adescriptor method:x.__get__(a).

Instance Binding

If binding to an object instance,a.x is transformed into the call:type(a).__dict__['x'].__get__(a,type(a)).

Class Binding

If binding to a class,A.x is transformed into the call:A.__dict__['x'].__get__(None,A).

Super Binding

A dotted lookup such assuper(A,a).x searchesa.__class__.__mro__ for a base classB followingA and thenreturnsB.__dict__['x'].__get__(a,A). If not a descriptor,x isreturned unchanged.

For instance bindings, the precedence of descriptor invocation depends onwhich descriptor methods are defined. A descriptor can define any combinationof__get__(),__set__() and__delete__(). If it does notdefine__get__(), then accessing the attribute will return the descriptorobject itself unless there is a value in the object’s instance dictionary. Ifthe descriptor defines__set__() and/or__delete__(), it is a datadescriptor; if it defines neither, it is a non-data descriptor. Normally, datadescriptors define both__get__() and__set__(), while non-datadescriptors have just the__get__() method. Data descriptors with__get__() and__set__() (and/or__delete__()) definedalways override a redefinition in aninstance dictionary. In contrast, non-data descriptors can be overridden byinstances.

Python methods (including those decorated with@staticmethod and@classmethod) areimplemented as non-data descriptors. Accordingly, instances can redefine andoverride methods. This allows individual instances to acquire behaviors thatdiffer from other instances of the same class.

Theproperty() function is implemented as a data descriptor. Accordingly,instances cannot override the behavior of a property.

3.3.2.4.__slots__

__slots__ allow us to explicitly declare data members (likeproperties) and deny the creation of__dict__ and__weakref__(unless explicitly declared in__slots__ or available in a parent.)

The space saved over using__dict__ can be significant.Attribute lookup speed can be significantly improved as well.

object.__slots__

This class variable can be assigned a string, iterable, or sequence ofstrings with variable names used by instances.__slots__ reserves spacefor the declared variables and prevents the automatic creation of__dict__and__weakref__ for each instance.

Notes on using__slots__:

  • When inheriting from a class without__slots__, the__dict__ and__weakref__ attribute of the instances will always be accessible.

  • Without a__dict__ variable, instances cannot be assigned newvariables notlisted in the__slots__ definition. Attempts to assign to an unlistedvariable name raisesAttributeError. If dynamic assignment of newvariables is desired, then add'__dict__' to the sequence of strings inthe__slots__ declaration.

  • Without a__weakref__ variable for each instance, classes defining__slots__ do not supportweakreferences to its instances.If weak referencesupport is needed, then add'__weakref__' to the sequence of strings in the__slots__ declaration.

  • __slots__ are implemented at the class level by creatingdescriptorsfor each variable name. As a result, class attributescannot be used to set default values for instance variables defined by__slots__; otherwise, the class attribute would overwrite the descriptorassignment.

  • The action of a__slots__ declaration is not limited to the classwhere it is defined.__slots__ declared in parents are available inchild classes. However, instances of a child subclass will get a__dict__ and__weakref__ unless the subclass also defines__slots__ (which should only contain names of anyadditional slots).

  • If a class defines a slot also defined in a base class, the instance variabledefined by the base class slot is inaccessible (except by retrieving itsdescriptor directly from the base class). This renders the meaning of theprogram undefined. In the future, a check may be added to prevent this.

  • TypeError will be raised if nonempty__slots__ are defined for aclass derived from a"variable-length"built-intype such asint,bytes, andtuple.

  • Any non-stringiterable may be assigned to__slots__.

  • If adictionary is used to assign__slots__, the dictionarykeys will be used as the slot names. The values of the dictionary can be usedto provide per-attribute docstrings that will be recognised byinspect.getdoc() and displayed in the output ofhelp().

  • __class__ assignment works only if both classes have thesame__slots__.

  • Multiple inheritance with multiple slotted parentclasses can be used,but only one parent is allowed to have attributes created by slots(the other bases must have empty slot layouts) - violations raiseTypeError.

  • If aniterator is used for__slots__ then adescriptor iscreated for eachof the iterator’s values. However, the__slots__ attribute will be an emptyiterator.

3.3.3.Customizing class creation

Whenever a class inherits from another class,__init_subclass__() iscalled on the parent class. This way, it is possible to write classes whichchange the behavior of subclasses. This is closely related to classdecorators, but where class decorators only affect the specific class they’reapplied to,__init_subclass__ solely applies to future subclasses of theclass defining the method.

classmethodobject.__init_subclass__(cls)

This method is called whenever the containing class is subclassed.cls is then the new subclass. If defined as a normal instance method,this method is implicitly converted to a class method.

Keyword arguments which are given to a new class are passed tothe parent class’s__init_subclass__. For compatibility withother classes using__init_subclass__, one should take out theneeded keyword arguments and pass the others over to the baseclass, as in:

classPhilosopher:def__init_subclass__(cls,/,default_name,**kwargs):super().__init_subclass__(**kwargs)cls.default_name=default_nameclassAustralianPhilosopher(Philosopher,default_name="Bruce"):pass

The default implementationobject.__init_subclass__ doesnothing, but raises an error if it is called with any arguments.

Note

The metaclass hintmetaclass is consumed by the rest of the typemachinery, and is never passed to__init_subclass__ implementations.The actual metaclass (rather than the explicit hint) can be accessed astype(cls).

Added in version 3.6.

When a class is created,type.__new__() scans the class variablesand makes callbacks to those with a__set_name__() hook.

object.__set_name__(self,owner,name)

Automatically called at the time the owning classowner iscreated. The object has been assigned toname in that class:

classA:x=C()# Automatically calls: x.__set_name__(A, 'x')

If the class variable is assigned after the class is created,__set_name__() will not be called automatically.If needed,__set_name__() can be called directly:

classA:passc=C()A.x=c# The hook is not calledc.__set_name__(A,'x')# Manually invoke the hook

SeeCreating the class object for more details.

Added in version 3.6.

3.3.3.1.Metaclasses

By default, classes are constructed usingtype(). The class body isexecuted in a new namespace and the class name is bound locally to theresult oftype(name,bases,namespace).

The class creation process can be customized by passing themetaclasskeyword argument in the class definition line, or by inheriting from anexisting class that included such an argument. In the following example,bothMyClass andMySubclass are instances ofMeta:

classMeta(type):passclassMyClass(metaclass=Meta):passclassMySubclass(MyClass):pass

Any other keyword arguments that are specified in the class definition arepassed through to all metaclass operations described below.

When a class definition is executed, the following steps occur:

  • MRO entries are resolved;

  • the appropriate metaclass is determined;

  • the class namespace is prepared;

  • the class body is executed;

  • the class object is created.

3.3.3.2.Resolving MRO entries

object.__mro_entries__(self,bases)

If a base that appears in a class definition is not an instance oftype, then an__mro_entries__() method is searched on the base.If an__mro_entries__() method is found, the base is substituted with theresult of a call to__mro_entries__() when creating the class.The method is called with the original bases tuplepassed to thebases parameter, and must return a tupleof classes that will be used instead of the base. The returned tuple may beempty: in these cases, the original base is ignored.

See also

types.resolve_bases()

Dynamically resolve bases that are not instances oftype.

types.get_original_bases()

Retrieve a class’s “original bases” prior to modifications by__mro_entries__().

PEP 560

Core support for typing module and generic types.

3.3.3.3.Determining the appropriate metaclass

The appropriate metaclass for a class definition is determined as follows:

  • if no bases and no explicit metaclass are given, thentype() is used;

  • if an explicit metaclass is given and it isnot an instance oftype(), then it is used directly as the metaclass;

  • if an instance oftype() is given as the explicit metaclass, orbases are defined, then the most derived metaclass is used.

The most derived metaclass is selected from the explicitly specifiedmetaclass (if any) and the metaclasses (i.e.type(cls)) of all specifiedbase classes. The most derived metaclass is one which is a subtype ofallof these candidate metaclasses. If none of the candidate metaclasses meetsthat criterion, then the class definition will fail withTypeError.

3.3.3.4.Preparing the class namespace

Once the appropriate metaclass has been identified, then the class namespaceis prepared. If the metaclass has a__prepare__ attribute, it is calledasnamespace=metaclass.__prepare__(name,bases,**kwds) (where theadditional keyword arguments, if any, come from the class definition). The__prepare__ method should be implemented as aclassmethod. Thenamespace returned by__prepare__ is passed in to__new__, but whenthe final class object is created the namespace is copied into a newdict.

If the metaclass has no__prepare__ attribute, then the class namespaceis initialised as an empty ordered mapping.

See also

PEP 3115 - Metaclasses in Python 3000

Introduced the__prepare__ namespace hook

3.3.3.5.Executing the class body

The class body is executed (approximately) asexec(body,globals(),namespace). The key difference from a normalcall toexec() is that lexical scoping allows the class body (includingany methods) to reference names from the current and outer scopes when theclass definition occurs inside a function.

However, even when the class definition occurs inside the function, methodsdefined inside the class still cannot see names defined at the class scope.Class variables must be accessed through the first parameter of instance orclass methods, or through the implicit lexically scoped__class__ referencedescribed in the next section.

3.3.3.6.Creating the class object

Once the class namespace has been populated by executing the class body,the class object is created by callingmetaclass(name,bases,namespace,**kwds) (the additional keywordspassed here are the same as those passed to__prepare__).

This class object is the one that will be referenced by the zero-argumentform ofsuper().__class__ is an implicit closure referencecreated by the compiler if any methods in a class body refer to either__class__ orsuper. This allows the zero argument form ofsuper() to correctly identify the class being defined based onlexical scoping, while the class or instance that was used to make thecurrent call is identified based on the first argument passed to the method.

CPython implementation detail: In CPython 3.6 and later, the__class__ cell is passed to the metaclassas a__classcell__ entry in the class namespace. If present, this mustbe propagated up to thetype.__new__ call in order for the class to beinitialised correctly.Failing to do so will result in aRuntimeError in Python 3.8.

When using the default metaclasstype, or any metaclass that ultimatelycallstype.__new__, the following additional customization steps areinvoked after creating the class object:

  1. Thetype.__new__ method collects all of the attributes in the classnamespace that define a__set_name__() method;

  2. Those__set_name__ methods are called with the classbeing defined and the assigned name of that particular attribute;

  3. The__init_subclass__() hook is called on theimmediate parent of the new class in its method resolution order.

After the class object is created, it is passed to the class decoratorsincluded in the class definition (if any) and the resulting object is boundin the local namespace as the defined class.

When a new class is created bytype.__new__, the object provided as thenamespace parameter is copied to a new ordered mapping and the originalobject is discarded. The new copy is wrapped in a read-only proxy, whichbecomes the__dict__ attribute of the class object.

See also

PEP 3135 - New super

Describes the implicit__class__ closure reference

3.3.3.7.Uses for metaclasses

The potential uses for metaclasses are boundless. Some ideas that have beenexplored include enum, logging, interface checking, automatic delegation,automatic property creation, proxies, frameworks, and automatic resourcelocking/synchronization.

3.3.4.Customizing instance and subclass checks

The following methods are used to override the default behavior of theisinstance() andissubclass() built-in functions.

In particular, the metaclassabc.ABCMeta implements these methods inorder to allow the addition of Abstract Base Classes (ABCs) as “virtual baseclasses” to any class or type (including built-in types), including otherABCs.

type.__instancecheck__(self,instance)

Return true ifinstance should be considered a (direct or indirect)instance ofclass. If defined, called to implementisinstance(instance,class).

type.__subclasscheck__(self,subclass)

Return true ifsubclass should be considered a (direct or indirect)subclass ofclass. If defined, called to implementissubclass(subclass,class).

Note that these methods are looked up on the type (metaclass) of a class. Theycannot be defined as class methods in the actual class. This is consistent withthe lookup of special methods that are called on instances, only in thiscase the instance is itself a class.

See also

PEP 3119 - Introducing Abstract Base Classes

Includes the specification for customizingisinstance() andissubclass() behavior through__instancecheck__() and__subclasscheck__(), with motivation for this functionalityin the context of adding Abstract Base Classes (see theabcmodule) to the language.

3.3.5.Emulating generic types

When usingtype annotations, it is often useful toparameterize ageneric type using Python’s square-brackets notation.For example, the annotationlist[int] might be used to signify alist in which all the elements are of typeint.

See also

PEP 484 - Type Hints

Introducing Python’s framework for type annotations

Generic Alias Types

Documentation for objects representing parameterized generic classes

Generics,user-defined generics andtyping.Generic

Documentation on how to implement generic classes that can beparameterized at runtime and understood by static type-checkers.

A class cangenerally only be parameterized if it defines the specialclass method__class_getitem__().

classmethodobject.__class_getitem__(cls,key)

Return an object representing the specialization of a generic classby type arguments found inkey.

When defined on a class,__class_getitem__() is automatically a classmethod. As such, there is no need for it to be decorated with@classmethod when it is defined.

3.3.5.1.The purpose of__class_getitem__

The purpose of__class_getitem__() is to allow runtimeparameterization of standard-library generic classes in order to more easilyapplytype hints to these classes.

To implement custom generic classes that can be parameterized at runtime andunderstood by static type-checkers, users should either inherit from a standardlibrary class that already implements__class_getitem__(), orinherit fromtyping.Generic, which has its own implementation of__class_getitem__().

Custom implementations of__class_getitem__() on classes definedoutside of the standard library may not be understood by third-partytype-checkers such as mypy. Using__class_getitem__() on any class forpurposes other than type hinting is discouraged.

3.3.5.2.__class_getitem__ versus__getitem__

Usually, thesubscription of an object using squarebrackets will call the__getitem__() instance method defined onthe object’s class. However, if the object being subscribed is itself a class,the class method__class_getitem__() may be called instead.__class_getitem__() should return aGenericAliasobject if it is properly defined.

Presented with theexpressionobj[x], the Python interpreterfollows something like the following process to decide whether__getitem__() or__class_getitem__() should becalled:

frominspectimportisclassdefsubscribe(obj,x):"""Return the result of the expression 'obj[x]'"""class_of_obj=type(obj)# If the class of obj defines __getitem__,# call class_of_obj.__getitem__(obj, x)ifhasattr(class_of_obj,'__getitem__'):returnclass_of_obj.__getitem__(obj,x)# Else, if obj is a class and defines __class_getitem__,# call obj.__class_getitem__(x)elifisclass(obj)andhasattr(obj,'__class_getitem__'):returnobj.__class_getitem__(x)# Else, raise an exceptionelse:raiseTypeError(f"'{class_of_obj.__name__}' object is not subscriptable")

In Python, all classes are themselves instances of other classes. The class ofa class is known as that class’smetaclass, and most classes have thetype class as their metaclass.type does not define__getitem__(), meaning that expressions such aslist[int],dict[str,float] andtuple[str,bytes] all result in__class_getitem__() being called:

>>># list has class "type" as its metaclass, like most classes:>>>type(list)<class 'type'>>>>type(dict)==type(list)==type(tuple)==type(str)==type(bytes)True>>># "list[int]" calls "list.__class_getitem__(int)">>>list[int]list[int]>>># list.__class_getitem__ returns a GenericAlias object:>>>type(list[int])<class 'types.GenericAlias'>

However, if a class has a custom metaclass that defines__getitem__(), subscribing the class may result in differentbehaviour. An example of this can be found in theenum module:

>>>fromenumimportEnum>>>classMenu(Enum):..."""A breakfast menu"""...SPAM='spam'...BACON='bacon'...>>># Enum classes have a custom metaclass:>>>type(Menu)<class 'enum.EnumMeta'>>>># EnumMeta defines __getitem__,>>># so __class_getitem__ is not called,>>># and the result is not a GenericAlias object:>>>Menu['SPAM']<Menu.SPAM: 'spam'>>>>type(Menu['SPAM'])<enum 'Menu'>

See also

PEP 560 - Core Support for typing module and generic types

Introducing__class_getitem__(), and outlining when asubscription results in__class_getitem__()being called instead of__getitem__()

3.3.6.Emulating callable objects

object.__call__(self[,args...])

Called when the instance is “called” as a function; if this method is defined,x(arg1,arg2,...) roughly translates totype(x).__call__(x,arg1,...).Theobject class itself does not provide this method.

3.3.7.Emulating container types

The following methods can be defined to implement container objects. None of themare provided by theobject class itself. Containers usually aresequences (such aslists ortuples) ormappings (likedictionaries),but can represent other containers as well. The first set of methods is usedeither to emulate a sequence or to emulate a mapping; the difference is that fora sequence, the allowable keys should be the integersk for which0<=k<N whereN is the length of the sequence, orslice objects, which define arange of items. It is also recommended that mappings provide the methodskeys(),values(),items(),get(),clear(),setdefault(),pop(),popitem(),copy(), andupdate() behaving similar to those for Python’s standarddictionaryobjects. Thecollections.abc module provides aMutableMappingabstract base class to help create those methods from a base set of__getitem__(),__setitem__(),__delitem__(), andkeys().Mutable sequences should provide methodsappend(),count(),index(),extend(),insert(),pop(),remove(),reverse() andsort(), like Python standardlistobjects. Finally,sequence types should implement addition (meaning concatenation) andmultiplication (meaning repetition) by defining the methods__add__(),__radd__(),__iadd__(),__mul__(),__rmul__() and__imul__()described below; they should not define other numericaloperators. It is recommended that both mappings and sequences implement the__contains__() method to allow efficient use of theinoperator; formappings,in should search the mapping’s keys; for sequences, it shouldsearch through the values. It is further recommended that both mappings andsequences implement the__iter__() method to allow efficient iterationthrough the container; for mappings,__iter__() should iteratethrough the object’s keys; for sequences, it should iterate through the values.

object.__len__(self)

Called to implement the built-in functionlen(). Should return the lengthof the object, an integer>= 0. Also, an object that doesn’t define a__bool__() method and whose__len__() method returns zero isconsidered to be false in a Boolean context.

CPython implementation detail: In CPython, the length is required to be at mostsys.maxsize.If the length is larger thansys.maxsize some features (such aslen()) may raiseOverflowError. To prevent raisingOverflowError by truth value testing, an object must define a__bool__() method.

object.__length_hint__(self)

Called to implementoperator.length_hint(). Should return an estimatedlength for the object (which may be greater or less than the actual length).The length must be an integer>= 0. The return value may also beNotImplemented, which is treated the same as if the__length_hint__ method didn’t exist at all. This method is purely anoptimization and is never required for correctness.

Added in version 3.4.

Note

Slicing is done exclusively with the following three methods. A call like

a[1:2]=b

is translated to

a[slice(1,2,None)]=b

and so forth. Missing slice items are always filled in withNone.

object.__getitem__(self,key)

Called to implement evaluation ofself[key]. Forsequence types,the accepted keys should be integers. Optionally, they may supportslice objects as well. Negative index support is also optional.Ifkey isof an inappropriate type,TypeError may be raised; ifkey is a valueoutside the set of indexes for the sequence (after any specialinterpretation of negative values),IndexError should be raised. Formapping types, ifkey is missing (not in the container),KeyError should be raised.

Note

for loops expect that anIndexError will be raised forillegal indexes to allow proper detection of the end of the sequence.

Note

Whensubscripting aclass, the specialclass method__class_getitem__() may be called instead of__getitem__(). See__class_getitem__ versus __getitem__ for moredetails.

object.__setitem__(self,key,value)

Called to implement assignment toself[key]. Same note as for__getitem__(). This should only be implemented for mappings if theobjects support changes to the values for keys, or if new keys can be added, orfor sequences if elements can be replaced. The same exceptions should be raisedfor improperkey values as for the__getitem__() method.

object.__delitem__(self,key)

Called to implement deletion ofself[key]. Same note as for__getitem__(). This should only be implemented for mappings if theobjects support removal of keys, or for sequences if elements can be removedfrom the sequence. The same exceptions should be raised for improperkeyvalues as for the__getitem__() method.

object.__missing__(self,key)

Called bydict.__getitem__() to implementself[key] for dict subclasseswhen key is not in the dictionary.

object.__iter__(self)

This method is called when aniterator is required for a container.This method should return a new iterator object that can iterate over all theobjects in the container. For mappings, it should iterate over the keys ofthe container.

object.__reversed__(self)

Called (if present) by thereversed() built-in to implementreverse iteration. It should return a new iterator object that iteratesover all the objects in the container in reverse order.

If the__reversed__() method is not provided, thereversed()built-in will fall back to using the sequence protocol (__len__() and__getitem__()). Objects that support the sequence protocol shouldonly provide__reversed__() if they can provide an implementationthat is more efficient than the one provided byreversed().

The membership test operators (in andnotin) are normallyimplemented as an iteration through a container. However, container objects cansupply the following special method with a more efficient implementation, whichalso does not require the object be iterable.

object.__contains__(self,item)

Called to implement membership test operators. Should return true ifitemis inself, false otherwise. For mapping objects, this should consider thekeys of the mapping rather than the values or the key-item pairs.

For objects that don’t define__contains__(), the membership test firsttries iteration via__iter__(), then the old sequence iterationprotocol via__getitem__(), seethis section in the languagereference.

3.3.8.Emulating numeric types

The following methods can be defined to emulate numeric objects. Methodscorresponding to operations that are not supported by the particular kind ofnumber implemented (e.g., bitwise operations for non-integral numbers) should beleft undefined.

object.__add__(self,other)
object.__sub__(self,other)
object.__mul__(self,other)
object.__matmul__(self,other)
object.__truediv__(self,other)
object.__floordiv__(self,other)
object.__mod__(self,other)
object.__divmod__(self,other)
object.__pow__(self,other[,modulo])
object.__lshift__(self,other)
object.__rshift__(self,other)
object.__and__(self,other)
object.__xor__(self,other)
object.__or__(self,other)

These methods are called to implement the binary arithmetic operations(+,-,*,@,/,//,%,divmod(),pow(),**,<<,>>,&,^,|). For instance, toevaluate the expressionx+y, wherex is an instance of a class thathas an__add__() method,type(x).__add__(x,y) is called. The__divmod__() method should be the equivalent to using__floordiv__() and__mod__(); it should not be related to__truediv__(). Note that__pow__() should be defined to acceptan optional third argument if the ternary version of the built-inpow()function is to be supported.

If one of those methods does not support the operation with the suppliedarguments, it should returnNotImplemented.

object.__radd__(self,other)
object.__rsub__(self,other)
object.__rmul__(self,other)
object.__rmatmul__(self,other)
object.__rtruediv__(self,other)
object.__rfloordiv__(self,other)
object.__rmod__(self,other)
object.__rdivmod__(self,other)
object.__rpow__(self,other[,modulo])
object.__rlshift__(self,other)
object.__rrshift__(self,other)
object.__rand__(self,other)
object.__rxor__(self,other)
object.__ror__(self,other)

These methods are called to implement the binary arithmetic operations(+,-,*,@,/,//,%,divmod(),pow(),**,<<,>>,&,^,|) with reflected(swapped) operands. These functions are only called if the left operand doesnot support the corresponding operation[3] and the operands are of differenttypes.[4] For instance, to evaluate the expressionx-y, wherey isan instance of a class that has an__rsub__() method,type(y).__rsub__(y,x) is called iftype(x).__sub__(x,y) returnsNotImplemented.

Note that ternarypow() will not try calling__rpow__() (thecoercion rules would become too complicated).

Note

If the right operand’s type is a subclass of the left operand’s type andthat subclass provides a different implementation of the reflected methodfor the operation, this method will be called before the left operand’snon-reflected method. This behavior allows subclasses to override theirancestors’ operations.

object.__iadd__(self,other)
object.__isub__(self,other)
object.__imul__(self,other)
object.__imatmul__(self,other)
object.__itruediv__(self,other)
object.__ifloordiv__(self,other)
object.__imod__(self,other)
object.__ipow__(self,other[,modulo])
object.__ilshift__(self,other)
object.__irshift__(self,other)
object.__iand__(self,other)
object.__ixor__(self,other)
object.__ior__(self,other)

These methods are called to implement the augmented arithmetic assignments(+=,-=,*=,@=,/=,//=,%=,**=,<<=,>>=,&=,^=,|=). These methods should attempt to do theoperation in-place (modifyingself) and return the result (which could be,but does not have to be,self). If a specific method is not defined, or ifthat method returnsNotImplemented, theaugmented assignment falls back to the normal methods. For instance, ifxis an instance of a class with an__iadd__() method,x+=y isequivalent tox=x.__iadd__(y) . If__iadd__() does not exist, or ifx.__iadd__(y)returnsNotImplemented,x.__add__(y) andy.__radd__(x) are considered, as with the evaluation ofx+y. Incertain situations, augmented assignment can result in unexpected errors (seeWhy does a_tuple[i] += [‘item’] raise an exception when the addition works?), but this behavior is in factpart of the data model.

object.__neg__(self)
object.__pos__(self)
object.__abs__(self)
object.__invert__(self)

Called to implement the unary arithmetic operations (-,+,abs()and~).

object.__complex__(self)
object.__int__(self)
object.__float__(self)

Called to implement the built-in functionscomplex(),int() andfloat(). Should return a valueof the appropriate type.

object.__index__(self)

Called to implementoperator.index(), and whenever Python needs tolosslessly convert the numeric object to an integer object (such as inslicing, or in the built-inbin(),hex() andoct()functions). Presence of this method indicates that the numeric object isan integer type. Must return an integer.

If__int__(),__float__() and__complex__() are notdefined then corresponding built-in functionsint(),float()andcomplex() fall back to__index__().

object.__round__(self[,ndigits])
object.__trunc__(self)
object.__floor__(self)
object.__ceil__(self)

Called to implement the built-in functionround() andmathfunctionstrunc(),floor() andceil().Unlessndigits is passed to__round__() all these methods shouldreturn the value of the object truncated to anIntegral(typically anint).

The built-in functionint() falls back to__trunc__() if neither__int__() nor__index__() is defined.

Changed in version 3.11:The delegation ofint() to__trunc__() is deprecated.

3.3.9.With Statement Context Managers

Acontext manager is an object that defines the runtime context to beestablished when executing awith statement. The context managerhandles the entry into, and the exit from, the desired runtime context for theexecution of the block of code. Context managers are normally invoked using thewith statement (described in sectionThe with statement), but can also beused by directly invoking their methods.

Typical uses of context managers include saving and restoring various kinds ofglobal state, locking and unlocking resources, closing opened files, etc.

For more information on context managers, seeContext Manager Types.Theobject class itself does not provide the context manager methods.

object.__enter__(self)

Enter the runtime context related to this object. Thewith statementwill bind this method’s return value to the target(s) specified in theas clause of the statement, if any.

object.__exit__(self,exc_type,exc_value,traceback)

Exit the runtime context related to this object. The parameters describe theexception that caused the context to be exited. If the context was exitedwithout an exception, all three arguments will beNone.

If an exception is supplied, and the method wishes to suppress the exception(i.e., prevent it from being propagated), it should return a true value.Otherwise, the exception will be processed normally upon exit from this method.

Note that__exit__() methods should not reraise the passed-in exception;this is the caller’s responsibility.

See also

PEP 343 - The “with” statement

The specification, background, and examples for the Pythonwithstatement.

3.3.10.Customizing positional arguments in class pattern matching

When using a class name in a pattern, positional arguments in the pattern are notallowed by default, i.e.caseMyClass(x,y) is typically invalid without specialsupport inMyClass. To be able to use that kind of pattern, the class needs todefine a__match_args__ attribute.

object.__match_args__

This class variable can be assigned a tuple of strings. When this class isused in a class pattern with positional arguments, each positional argument willbe converted into a keyword argument, using the corresponding value in__match_args__ as the keyword. The absence of this attribute is equivalent tosetting it to().

For example, ifMyClass.__match_args__ is("left","center","right") that meansthatcaseMyClass(x,y) is equivalent tocaseMyClass(left=x,center=y). Notethat the number of arguments in the pattern must be smaller than or equal to the numberof elements in__match_args__; if it is larger, the pattern match attempt will raiseaTypeError.

Added in version 3.10.

See also

PEP 634 - Structural Pattern Matching

The specification for the Pythonmatch statement.

3.3.11.Emulating buffer types

Thebuffer protocol provides a way for Pythonobjects to expose efficient access to a low-level memory array. This protocolis implemented by builtin types such asbytes andmemoryview,and third-party libraries may define additional buffer types.

While buffer types are usually implemented in C, it is also possible toimplement the protocol in Python.

object.__buffer__(self,flags)

Called when a buffer is requested fromself (for example, by thememoryview constructor). Theflags argument is an integerrepresenting the kind of buffer requested, affecting for example whetherthe returned buffer is read-only or writable.inspect.BufferFlagsprovides a convenient way to interpret the flags. The method must returnamemoryview object.

object.__release_buffer__(self,buffer)

Called when a buffer is no longer needed. Thebuffer argument is amemoryview object that was previously returned by__buffer__(). The method must release any resources associatedwith the buffer. This method should returnNone.Buffer objects that do not need to perform any cleanup are not requiredto implement this method.

Added in version 3.12.

See also

PEP 688 - Making the buffer protocol accessible in Python

Introduces the Python__buffer__ and__release_buffer__ methods.

collections.abc.Buffer

ABC for buffer types.

3.3.12.Special method lookup

For custom classes, implicit invocations of special methods are only guaranteedto work correctly if defined on an object’s type, not in the object’s instancedictionary. That behaviour is the reason why the following code raises anexception:

>>>classC:...pass...>>>c=C()>>>c.__len__=lambda:5>>>len(c)Traceback (most recent call last):  File"<stdin>", line1, in<module>TypeError:object of type 'C' has no len()

The rationale behind this behaviour lies with a number of special methods suchas__hash__() and__repr__() that are implementedby all objects,including type objects. If the implicit lookup of these methods used theconventional lookup process, they would fail when invoked on the type objectitself:

>>>1.__hash__()==hash(1)True>>>int.__hash__()==hash(int)Traceback (most recent call last):  File"<stdin>", line1, in<module>TypeError:descriptor '__hash__' of 'int' object needs an argument

Incorrectly attempting to invoke an unbound method of a class in this way issometimes referred to as ‘metaclass confusion’, and is avoided by bypassingthe instance when looking up special methods:

>>>type(1).__hash__(1)==hash(1)True>>>type(int).__hash__(int)==hash(int)True

In addition to bypassing any instance attributes in the interest ofcorrectness, implicit special method lookup generally also bypasses the__getattribute__() method even of the object’s metaclass:

>>>classMeta(type):...def__getattribute__(*args):...print("Metaclass getattribute invoked")...returntype.__getattribute__(*args)...>>>classC(object,metaclass=Meta):...def__len__(self):...return10...def__getattribute__(*args):...print("Class getattribute invoked")...returnobject.__getattribute__(*args)...>>>c=C()>>>c.__len__()# Explicit lookup via instanceClass getattribute invoked10>>>type(c).__len__(c)# Explicit lookup via typeMetaclass getattribute invoked10>>>len(c)# Implicit lookup10

Bypassing the__getattribute__() machinery in this fashionprovides significant scope for speed optimisations within theinterpreter, at the cost of some flexibility in the handling ofspecial methods (the special methodmust be set on the classobject itself in order to be consistently invoked by the interpreter).

3.4.Coroutines

3.4.1.Awaitable Objects

Anawaitable object generally implements an__await__() method.Coroutine objects returned fromasyncdef functionsare awaitable.

Note

Thegenerator iterator objects returned from generatorsdecorated withtypes.coroutine()are also awaitable, but they do not implement__await__().

object.__await__(self)

Must return aniterator. Should be used to implementawaitable objects. For instance,asyncio.Future implementsthis method to be compatible with theawait expression.Theobject class itself is not awaitable and does not providethis method.

Note

The language doesn’t place any restriction on the type or value of theobjects yielded by the iterator returned by__await__, as this isspecific to the implementation of the asynchronous execution framework(e.g.asyncio) that will be managing theawaitable object.

Added in version 3.5.

See also

PEP 492 for additional information about awaitable objects.

3.4.2.Coroutine Objects

Coroutine objects areawaitable objects.A coroutine’s execution can be controlled by calling__await__() anditerating over the result. When the coroutine has finished executing andreturns, the iterator raisesStopIteration, and the exception’svalue attribute holds the return value. If thecoroutine raises an exception, it is propagated by the iterator. Coroutinesshould not directly raise unhandledStopIteration exceptions.

Coroutines also have the methods listed below, which are analogous tothose of generators (seeGenerator-iterator methods). However, unlikegenerators, coroutines do not directly support iteration.

Changed in version 3.5.2:It is aRuntimeError to await on a coroutine more than once.

coroutine.send(value)

Starts or resumes execution of the coroutine. Ifvalue isNone,this is equivalent to advancing the iterator returned by__await__(). Ifvalue is notNone, this method delegatesto thesend() method of the iterator that causedthe coroutine to suspend. The result (return value,StopIteration, or other exception) is the same as wheniterating over the__await__() return value, described above.

coroutine.throw(value)
coroutine.throw(type[,value[,traceback]])

Raises the specified exception in the coroutine. This method delegatesto thethrow() method of the iterator that causedthe coroutine to suspend, if it has such a method. Otherwise,the exception is raised at the suspension point. The result(return value,StopIteration, or other exception) is the same aswhen iterating over the__await__() return value, describedabove. If the exception is not caught in the coroutine, it propagatesback to the caller.

Changed in version 3.12:The second signature (type[, value[, traceback]]) is deprecated andmay be removed in a future version of Python.

coroutine.close()

Causes the coroutine to clean itself up and exit. If the coroutineis suspended, this method first delegates to theclose()method of the iterator that caused the coroutine to suspend, if ithas such a method. Then it raisesGeneratorExit at thesuspension point, causing the coroutine to immediately clean itself up.Finally, the coroutine is marked as having finished executing, even ifit was never started.

Coroutine objects are automatically closed using the above process whenthey are about to be destroyed.

3.4.3.Asynchronous Iterators

Anasynchronous iterator can call asynchronous code inits__anext__ method.

Asynchronous iterators can be used in anasyncfor statement.

Theobject class itself does not provide these methods.

object.__aiter__(self)

Must return anasynchronous iterator object.

object.__anext__(self)

Must return anawaitable resulting in a next value of the iterator. Shouldraise aStopAsyncIteration error when the iteration is over.

An example of an asynchronous iterable object:

classReader:asyncdefreadline(self):...def__aiter__(self):returnselfasyncdef__anext__(self):val=awaitself.readline()ifval==b'':raiseStopAsyncIterationreturnval

Added in version 3.5.

Changed in version 3.7:Prior to Python 3.7,__aiter__() could return anawaitablethat would resolve to anasynchronous iterator.

Starting with Python 3.7,__aiter__() must return anasynchronous iterator object. Returning anything elsewill result in aTypeError error.

3.4.4.Asynchronous Context Managers

Anasynchronous context manager is acontext manager that is able tosuspend execution in its__aenter__ and__aexit__ methods.

Asynchronous context managers can be used in anasyncwith statement.

Theobject class itself does not provide these methods.

object.__aenter__(self)

Semantically similar to__enter__(), the onlydifference being that it must return anawaitable.

object.__aexit__(self,exc_type,exc_value,traceback)

Semantically similar to__exit__(), the onlydifference being that it must return anawaitable.

An example of an asynchronous context manager class:

classAsyncContextManager:asyncdef__aenter__(self):awaitlog('entering context')asyncdef__aexit__(self,exc_type,exc,tb):awaitlog('exiting context')

Added in version 3.5.

Footnotes

[1]

Itis possible in some cases to change an object’s type, under certaincontrolled conditions. It generally isn’t a good idea though, since it canlead to some very strange behaviour if it is handled incorrectly.

[2]

The__hash__(),__iter__(),__reversed__(),__contains__(),__class_getitem__() and__fspath__()methods have special handling for this. Otherswill still raise aTypeError, but may do so by relying onthe behavior thatNone is not callable.

[3]

“Does not support” here means that the class has no such method, orthe method returnsNotImplemented. Do not set the method toNone if you want to force fallback to the right operand’s reflectedmethod—that will instead have the opposite effect of explicitlyblocking such fallback.

[4]

For operands of the same type, it is assumed that if the non-reflectedmethod – such as__add__() – fails then the overalloperation is notsupported, which is why the reflected method is not called.