Process-Global State

C-level static variables. Since this is very low-level memory storage, it must be managed carefully.

Per-module State

State local to a module object, allocated dynamically as part of a module object’s initialization. This isolates the state from other instances of the module (including those in other subinterpreters).

Accessed by PyModule_GetState().

Static Type

A type object defined as a C-level static variable, i.e. a compiled-in type object.

A static type needs to be shared between module instances and has no information of what module it belongs to. Static types do not have __dict__ (although their instances might).

Heap Type

A type object created at run time.

Defining Class

The defining class of a method (either bound or unbound) is the class on which the method was defined. A class that merely inherits the method from its base is not the defining class.

For example, int is the defining class of True.to_bytes, True.__floor__ and int.__repr__.

In C, the defining class is the one defined with the corresponding tp_methods or “tp slots” [1] entry. For methods defined in Python, the defining class is saved in the __class__ closure cell.

C-API

The “Python/C API” as described in Python documentation. CPython implements the C-API, but other implementations exist.

Slot methods

The above changes don’t cover slot methods, such as tp_iter or nb_add.

The problem with slot methods is that their C API is fixed, so we can’t simply add a new argument to pass in the defining class. Two possible solutions have been proposed to this problem:

• Look up the class through walking the MRO. This is potentially expensive, but will be usable if performance is not a problem (such as when raising a module-level exception).
• Storing a pointer to the defining class of each slot in a separate table, __typeslots__ [2]. This is technically feasible and fast, but quite invasive.

Modules affected by this concern also have the option of using thread-local state or PEP 567 context variables as a caching mechanism, or else defining their own reload-friendly lookup caching scheme.

Solving the issue generally is deferred to a future PEP.

Adding module references to heap types

A new factory method will be added to the C-API for creating modules:

PyObject* PyType_FromModuleAndSpec(PyObject *module,
                                   PyType_Spec *spec,
                                   PyObject *bases)

This acts the same as PyType_FromSpecWithBases, and additionally associates the provided module object with the new type. (In CPython, this will set ht_module described below.)

Additionally, an accessor, PyObject * PyType_GetModule(PyTypeObject *) will be provided. It will return the type’s associated module if one is set, otherwise it will set TypeError and return NULL. When given a static type, it will always set TypeError and return NULL.

To implement this in CPython, the PyHeapTypeObject struct will get a new member, PyObject *ht_module, that will store a pointer to the associated module. It will be NULL by default and should not be modified after the type object is created.

The ht_module member will not be inherited by subclasses; it needs to be set using PyType_FromSpecWithBases for each individual type that needs it.

Usually, creating a class with ht_module set will create a reference cycle involving the class and the module. This is not a problem, as tearing down modules is not a performance-sensitive operation, and module-level functions typically also create reference cycles. The existing “set all module globals to None” code that breaks function cycles through f_globals will also break the new cycles through ht_module.

Passing the defining class to extension methods

A new signature flag, METH_METHOD, will be added for use in PyMethodDef.ml_flags. Conceptually, it adds defining_class to the function signature. To make the initial implementation easier, the flag can only be used as (METH_FASTCALL | METH_KEYWORDS | METH_METHOD). (It can’t be used with other flags like METH_O or bare METH_FASTCALL, though it may be combined with METH_CLASS or METH_STATIC).

C functions for methods defined using this flag combination will be called using a new C signature called PyCMethod:

PyObject *PyCMethod(PyObject *self,
                    PyTypeObject *defining_class,
                    PyObject *const *args,
                    size_t nargsf,
                    PyObject *kwnames)

Additional combinations like (METH_VARARGS | METH_METHOD) may be added in the future (or even in the initial implementation of this PEP). However, METH_METHOD should always be an additional flag, i.e., the defining class should only be passed in if needed.

In CPython, a new structure extending PyCFunctionObject will be added to hold the extra information:

typedef struct {
    PyCFunctionObject func;
    PyTypeObject *mm_class; /* Passed as 'defining_class' arg to the C func */
} PyCMethodObject;

The PyCFunction implementation will pass mm_class into a PyCMethod C function when it finds the METH_METHOD flag being set. A new macro PyCFunction_GET_CLASS(cls) will be added for easier access to mm_class.

C methods may continue to use the other METH_* signatures if they do not require access to their defining class/module. If METH_METHOD is not set, casting to PyCMethodObject is invalid.

Argument Clinic

To support passing the defining class to methods using Argument Clinic, a new converter called defining_class will be added to CPython’s Argument Clinic tool.

Each method may only have one argument using this converter, and it must appear after self, or, if self is not used, as the first argument. The argument will be of type PyTypeObject *.

When used, Argument Clinic will select METH_FASTCALL | METH_KEYWORDS | METH_METHOD as the calling convention. The argument will not appear in __text_signature__.

The new converter will initially not be compatible with __init__ and __new__ methods, which cannot use the METH_METHOD convention.

Helpers

Getting to per-module state from a heap type is a very common task. To make this easier, a helper will be added:

void *PyType_GetModuleState(PyObject *type)

This function takes a heap type and on success, it returns pointer to the state of the module that the heap type belongs to.

On failure, two scenarios may occur. When a non-type object, or a type without a module is passed in, TypeError is set and NULL returned. If the module is found, the pointer to the state, which may be NULL, is returned without setting any exception.

Modules Converted in the Initial Implementation

To validate the approach, the _elementtree module will be modified during the initial implementation.

Slot methods

A way of passing defining class (or module state) to slot methods may be added in the future.

A previous version of this PEP proposed a helper function that would determine a defining class by searching the MRO for a class that defines a slot to a particular function. However, this approach would fail if a class is mutated (which is, for heap types, possible from Python code). Solving this problem is left to future discussions.

Easy creation of types with module references

It would be possible to add a PEP 489 execution slot type to make creating heap types significantly easier than calling PyType_FromModuleAndSpec. This is left to a future PEP.

It may be good to add a good way to create static exception types from the limited API. Such exception types could be shared between subinterpreters, but instantiated without needing specific module state. This is also left to possible future discussions.

Optimization

As proposed here, methods defined with the METH_METHOD flag only support one specific signature.

If it turns out that other signatures are needed for performance reasons, they may be added.