Skip to main content
`Ctrl`+`K`

# Python types and C-structures

Several new types are defined in the C-code. Most of these are accessible from Python, but a few are not exposed due to their limited use. Every new Python type has an associated PyObject* with an internal structure that includes a pointer to a “method table” that defines how the new object behaves in Python. When you receive a Python object into C code, you always get a pointer to a `PyObject` structure. Because a `PyObject` structure is very generic and defines only `PyObject_HEAD`, by itself it is not very interesting. However, different objects contain more details after the `PyObject_HEAD` (but you have to cast to the correct type to access them — or use accessor functions or macros).

## New Python types defined

Python types are the functional equivalent in C of classes in Python. By constructing a new Python type you make available a new object for Python. The ndarray object is an example of a new type defined in C. New types are defined in C by two basic steps:

1. creating a C-structure (usually named `Py{Name}Object`) that is binary- compatible with the `PyObject` structure itself but holds the additional information needed for that particular object;

2. populating the `PyTypeObject` table (pointed to by the ob_type member of the `PyObject` structure) with pointers to functions that implement the desired behavior for the type.

Instead of special method names which define behavior for Python classes, there are “function tables” which point to functions that implement the desired results. The PyTypeObject itself is dynamic which allows C types that can be “sub-typed” from other C-types in C, and sub-classed in Python. The children types inherit the attributes and methods from their parent(s).

There are two major new types: the ndarray ( `PyArray_Type` ) and the ufunc ( `PyUFunc_Type` ). Additional types play a supportive role: the `PyArrayIter_Type`, the `PyArrayMultiIter_Type`, and the `PyArrayDescr_Type` . The `PyArrayIter_Type` is the type for a flat iterator for an ndarray (the object that is returned when getting the flat attribute). The `PyArrayMultiIter_Type` is the type of the object returned when calling `broadcast`. It handles iteration and broadcasting over a collection of nested sequences. Also, the `PyArrayDescr_Type` is the data-type-descriptor type whose instances describe the data and `PyArray_DTypeMeta` is the metaclass for data-type descriptors. There are also new scalar-array types which are new Python scalars corresponding to each of the fundamental data types available for arrays. Additional types are placeholders that allow the array scalars to fit into a hierarchy of actual Python types. Finally, the `PyArray_DTypeMeta` instances corresponding to the NumPy built-in data types are also publicly visible.

### PyArray_Type and PyArrayObject

PyTypeObject PyArray_Type

  The Python type of the ndarray is `PyArray_Type`. In C, every ndarray is a pointer to a `PyArrayObject` structure. The ob_type member of this structure contains a pointer to the `PyArray_Type` typeobject.

type PyArrayObject
type NPY_AO

  The `PyArrayObject` C-structure contains all of the required information for an array. All instances of an ndarray (and its subclasses) will have this structure. For future compatibility, these structure members should normally be accessed using the provided macros. If you need a shorter name, then you can make use of `NPY_AO` (deprecated) which is defined to be equivalent to `PyArrayObject`. Direct access to the struct fields are deprecated. Use the `PyArray_*(arr)` form instead. As of NumPy 1.20, the size of this struct is not considered part of the NumPy ABI (see note at the end of the member list).

      typedef struct PyArrayObject {
          PyObject_HEAD
          char *data;
          int nd;
          npy_intp *dimensions;
          npy_intp *strides;
          PyObject *base;
          PyArray_Descr *descr;
          int flags;
          PyObject *weakreflist;
          /* version dependent private members */
      } PyArrayObject;

  `PyObject_HEAD`

    This is needed by all Python objects. It consists of (at least) a reference count member ( `ob_refcnt` ) and a pointer to the typeobject ( `ob_type` ). (Other elements may also be present if Python was compiled with special options see Include/object.h in the Python source tree for more information). The ob_type member points to a Python type object.

  char *data

    Accessible via `PyArray_DATA`, this data member is a pointer to the first element of the array. This pointer can (and normally should) be recast to the data type of the array.

  int nd

    An integer providing the number of dimensions for this array. When nd is 0, the array is sometimes called a rank-0 array. Such arrays have undefined dimensions and strides and cannot be accessed. Macro `PyArray_NDIM` defined in `ndarraytypes.h` points to this data member. `NPY_MAXDIMS` is defined as a compile time constant limiting the number of dimensions. This number is 64 since NumPy 2 and was 32 before. However, we may wish to remove this limitations in the future so that it is best to explicitly check dimensionality for code that relies on such an upper bound.

  npy_intp *dimensions

    An array of integers providing the shape in each dimension as long as nd \(\geq\) 1. The integer is always large enough to hold a pointer on the platform, so the dimension size is only limited by memory. `PyArray_DIMS` is the macro associated with this data member.

  npy_intp *strides

    An array of integers providing for each dimension the number of bytes that must be skipped to get to the next element in that dimension. Associated with macro `PyArray_STRIDES`.

  PyObject *base

    Pointed to by `PyArray_BASE`, this member is used to hold a pointer to another Python object that is related to this array. There are two use cases:

    - If this array does not own its own memory, then base points to the Python object that owns it (perhaps another array object)

    - If this array has the `NPY_ARRAY_WRITEBACKIFCOPY` flag set, then this array is a working copy of a “misbehaved” array.

    When `PyArray_ResolveWritebackIfCopy` is called, the array pointed to by base will be updated with the contents of this array.

  PyArray_Descr *descr

    A pointer to a data-type descriptor object (see below). The data-type descriptor object is an instance of a new built-in type which allows a generic description of memory. There is a descriptor structure for each data type supported. This descriptor structure contains useful information about the type as well as a pointer to a table of function pointers to implement specific functionality. As the name suggests, it is associated with the macro `PyArray_DESCR`.

  int flags

    Pointed to by the macro `PyArray_FLAGS`, this data member represents the flags indicating how the memory pointed to by data is to be interpreted. Possible flags are `NPY_ARRAY_C_CONTIGUOUS`, `NPY_ARRAY_F_CONTIGUOUS`, `NPY_ARRAY_OWNDATA`, `NPY_ARRAY_ALIGNED`, `NPY_ARRAY_WRITEABLE`, `NPY_ARRAY_WRITEBACKIFCOPY`.

  PyObject *weakreflist

    This member allows array objects to have weak references (using the weakref module).

  Note

  Further members are considered private and version dependent. If the size of the struct is important for your code, special care must be taken. A possible use-case when this is relevant is subclassing in C. If your code relies on `sizeof(PyArrayObject)` to be constant, you must add the following check at import time:

      if (sizeof(PyArrayObject) < PyArray_Type.tp_basicsize) {
          PyErr_SetString(PyExc_ImportError,
             "Binary incompatibility with NumPy, must recompile/update X.");
          return NULL;
      }

  To ensure that your code does not have to be compiled for a specific NumPy version, you may add a constant, leaving room for changes in NumPy. A solution guaranteed to be compatible with any future NumPy version requires the use of a runtime calculate offset and allocation size.

The `PyArray_Type` typeobject implements many of the features of `Python objects` including the `tp_as_number`, `tp_as_sequence`, `tp_as_mapping`, and `tp_as_buffer` interfaces. The `rich comparison`) is also used along with new-style attribute lookup for member (`tp_members`) and properties (`tp_getset`). The `PyArray_Type` can also be sub-typed.

Tip

The `tp_as_number` methods use a generic approach to call whatever function has been registered for handling the operation. When the `_multiarray_umath` module is imported, it sets the numeric operations for all arrays to the corresponding ufuncs. This choice can be changed with `PyUFunc_ReplaceLoopBySignature`.

### PyGenericArrType_Type

PyTypeObject PyGenericArrType_Type

  The `PyGenericArrType_Type` is the PyTypeObject definition which create the `numpy.generic` python type.

### PyArrayDescr_Type and PyArray_Descr

PyTypeObject PyArrayDescr_Type

  The `PyArrayDescr_Type` is the built-in type of the data-type-descriptor objects used to describe how the bytes comprising the array are to be interpreted. There are 21 statically-defined `PyArray_Descr` objects for the built-in data-types. While these participate in reference counting, their reference count should never reach zero. There is also a dynamic table of user-defined `PyArray_Descr` objects that is also maintained. Once a data-type-descriptor object is “registered” it should never be deallocated either. The function `PyArray_DescrFromType` (…) can be used to retrieve a `PyArray_Descr` object from an enumerated type-number (either built-in or user- defined).

type PyArray_DescrProto

  Identical structure to `PyArray_Descr`. This struct is used for static definition of a prototype for registering a new legacy DType by `PyArray_RegisterDataType`.

  See the note in `PyArray_RegisterDataType` for details.

type PyArray_Descr

  The `PyArray_Descr` structure lies at the heart of the `PyArrayDescr_Type`. While it is described here for completeness, it should be considered internal to NumPy and manipulated via `PyArrayDescr_*` or `PyDataType*` functions and macros. The size of this structure is subject to change across versions of NumPy. To ensure compatibility:

  - Never declare a non-pointer instance of the struct

  - Never perform pointer arithmetic

  - Never use `sizeof(PyArray_Descr)`

  It has the following structure:

      typedef struct {
          PyObject_HEAD
          PyTypeObject *typeobj;
          char kind;
          char type;
          char byteorder;
          char _former_flags;  // unused field
          int type_num;
          /*
           * Definitions after this one must be accessed through accessor
           * functions (see below) when compiling with NumPy 1.x support.
           */
          npy_uint64 flags;
          npy_intp elsize;
          npy_intp alignment;
          NpyAuxData *c_metadata;
          npy_hash_t hash;
          void *reserved_null[2];  // unused field, must be NULLed.
      } PyArray_Descr;

  Some dtypes have additional members which are accessible through PyDataType_NAMES, PyDataType_FIELDS, PyDataType_SUBARRAY, and in some cases (times) PyDataType_C_METADATA.

  PyTypeObject *typeobj

    Pointer to a typeobject that is the corresponding Python type for the elements of this array. For the builtin types, this points to the corresponding array scalar. For user-defined types, this should point to a user-defined typeobject. This typeobject can either inherit from array scalars or not. If it does not inherit from array scalars, then the `NPY_USE_GETITEM` and `NPY_USE_SETITEM` flags should be set in the `flags` member.

  char kind

    A character code indicating the kind of array (using the array interface typestring notation). A ‘b’ represents Boolean, a ‘i’ represents signed integer, a ‘u’ represents unsigned integer, ‘f’ represents floating point, ‘c’ represents complex floating point, ‘S’ represents 8-bit zero-terminated bytes, ‘U’ represents 32-bit/character unicode string, and ‘V’ represents arbitrary.

  char type

    A traditional character code indicating the data type.

  char byteorder

    A character indicating the byte-order: ‘>’ (big-endian), ‘<’ (little- endian), ‘=’ (native), ‘|’ (irrelevant, ignore). All builtin data- types have byteorder ‘=’.

  npy_uint64 flags

    A data-type bit-flag that determines if the data-type exhibits object- array like behavior. Each bit in this member is a flag which are named as:

    - `NPY_ITEM_REFCOUNT`

    - `NPY_ITEM_HASOBJECT`

    - `NPY_LIST_PICKLE`

    - `NPY_ITEM_IS_POINTER`

    - `NPY_NEEDS_INIT`

    - `NPY_NEEDS_PYAPI`

    - `NPY_USE_GETITEM`

    - `NPY_USE_SETITEM`

    - `NPY_FROM_FIELDS`

    - `NPY_OBJECT_DTYPE_FLAGS`

  int type_num

    A number that uniquely identifies the data type. For new data-types, this number is assigned when the data-type is registered.

  npy_intp elsize

    For data types that are always the same size (such as long), this holds the size of the data type. For flexible data types where different arrays can have a different elementsize, this should be 0.

    See PyDataType_ELSIZE and PyDataType_SET_ELSIZE for a way to access this field in a NumPy 1.x compatible way.

  npy_intp alignment

    A number providing alignment information for this data type. Specifically, it shows how far from the start of a 2-element structure (whose first element is a `char` ), the compiler places an item of this type: `offsetof(struct {char c; type v;}, v)`

    See `PyDataType_ALIGNMENT` for a way to access this field in a NumPy 1.x compatible way.

  PyObject *metadata

    Metadata about this dtype.

  NpyAuxData *c_metadata

    Metadata specific to the C implementation of the particular dtype. Added for NumPy 1.7.0.

  type npy_hash_t
  npy_hash_t *hash

    Used for caching hash values.

NPY_ITEM_REFCOUNT

  Indicates that items of this data-type must be reference counted (using `Py_INCREF` and `Py_DECREF` ).

NPY_ITEM_HASOBJECT

  Same as `NPY_ITEM_REFCOUNT`.

NPY_LIST_PICKLE

  Indicates arrays of this data-type must be converted to a list before pickling.

NPY_ITEM_IS_POINTER

  Indicates the item is a pointer to some other data-type

NPY_NEEDS_INIT

  Indicates memory for this data-type must be initialized (set to 0) on creation.

NPY_NEEDS_PYAPI

  Indicates this data-type requires the Python C-API during access (so don’t give up the GIL if array access is going to be needed).

NPY_USE_GETITEM

  On array access use the `f->getitem` function pointer instead of the standard conversion to an array scalar. Must use if you don’t define an array scalar to go along with the data-type.

NPY_USE_SETITEM

  When creating a 0-d array from an array scalar use `f->setitem` instead of the standard copy from an array scalar. Must use if you don’t define an array scalar to go along with the data-type.

NPY_FROM_FIELDS

  The bits that are inherited for the parent data-type if these bits are set in any field of the data-type. Currently ( `NPY_NEEDS_INIT` | `NPY_LIST_PICKLE` | `NPY_ITEM_REFCOUNT` | `NPY_NEEDS_PYAPI` ).

NPY_OBJECT_DTYPE_FLAGS

  Bits set for the object data-type: ( `NPY_LIST_PICKLE` | `NPY_USE_GETITEM` | `NPY_ITEM_IS_POINTER` | `NPY_ITEM_REFCOUNT` | `NPY_NEEDS_INIT` | `NPY_NEEDS_PYAPI`).

int PyDataType_FLAGCHK(PyArray_Descr *dtype, int flags)

  Return true if all the given flags are set for the data-type object.

int PyDataType_REFCHK(PyArray_Descr *dtype)

  Equivalent to `PyDataType_FLAGCHK` (dtype, `NPY_ITEM_REFCOUNT`).

### PyArray_ArrFuncs

PyArray_ArrFuncs *PyDataType_GetArrFuncs(PyArray_Descr *dtype)

  Fetch the legacy PyArray_ArrFuncs of the datatype (cannot fail).

  Added in version NumPy: 2.0 This function was added in a backwards compatible and backportable way in NumPy 2.0 (see `npy_2_compat.h`). Any code that previously accessed the `->f` slot of the `PyArray_Descr`, must now use this function and backport it to compile with 1.x. (The `npy_2_compat.h` header can be vendored for this purpose.)

type PyArray_ArrFuncs

  Functions implementing internal features. Not all of these function pointers must be defined for a given type. The required members are `nonzero`, `copyswap`, `copyswapn`, `setitem`, `getitem`, and `cast`. These are assumed to be non- `NULL` and `NULL` entries will cause a program crash. The other functions may be `NULL` which will just mean reduced functionality for that data-type. (Also, the nonzero function will be filled in with a default function if it is `NULL` when you register a user-defined data-type).

      typedef struct {
          PyArray_VectorUnaryFunc *cast[NPY_NTYPES_LEGACY];
          PyArray_GetItemFunc *getitem;
          PyArray_SetItemFunc *setitem;
          PyArray_CopySwapNFunc *copyswapn;
          PyArray_CopySwapFunc *copyswap;
          PyArray_CompareFunc *compare;
          PyArray_ArgFunc *argmax;
          PyArray_DotFunc *dotfunc;
          PyArray_ScanFunc *scanfunc;
          PyArray_FromStrFunc *fromstr;
          PyArray_NonzeroFunc *nonzero;
          PyArray_FillFunc *fill;
          PyArray_FillWithScalarFunc *fillwithscalar;
          PyArray_SortFunc *sort[NPY_NSORTS];
          PyArray_ArgSortFunc *argsort[NPY_NSORTS];
          PyObject *castdict;
          PyArray_ScalarKindFunc *scalarkind;
          int **cancastscalarkindto;
          int *cancastto;
          void *_unused1;
          void *_unused2;
          void *_unused3;
          PyArray_ArgFunc *argmin;
      } PyArray_ArrFuncs;

  The concept of a behaved segment is used in the description of the function pointers. A behaved segment is one that is aligned and in native machine byte-order for the data-type. The `nonzero`, `copyswap`, `copyswapn`, `getitem`, and `setitem` functions can (and must) deal with mis-behaved arrays. The other functions require behaved memory segments.

  Note

  The functions are largely legacy API, however, some are still used. As of NumPy 2.x they are only available via PyDataType_GetArrFuncs (see the function for more details). Before using any function defined in the struct you should check whether it is `NULL`. In general, the functions `getitem`, `setitem`, `copyswap`, and `copyswapn` can be expected to be defined, but all functions are expected to be replaced with newer API. For example, `PyArray_Pack` is a more powerful version of `setitem` that for example correctly deals with casts.

  void cast(void *from, void *to, npy_intp n, void *fromarr, void *toarr)

    An array of function pointers to cast from the current type to all of the other builtin types. Each function casts a contiguous, aligned, and notswapped buffer pointed at by from to a contiguous, aligned, and notswapped buffer pointed at by to The number of items to cast is given by n, and the arguments fromarr and toarr are interpreted as PyArrayObjects for flexible arrays to get itemsize information.

  PyObject *getitem(void *data, void *arr)

    A pointer to a function that returns a standard Python object from a single element of the array object arr pointed to by data. This function must be able to deal with “misbehaved “(misaligned and/or swapped) arrays correctly.

  int setitem(PyObject *item, void *data, void *arr)

    A pointer to a function that sets the Python object item into the array, arr, at the position pointed to by data . This function deals with “misbehaved” arrays. If successful, a zero is returned, otherwise, a negative one is returned (and a Python error set).

  void copyswapn(void *dest, npy_intp dstride, void *src, npy_intp sstride, npy_intp n, int swap, void *arr)
  void copyswap(void *dest, void *src, int swap, void *arr)

    These members are both pointers to functions to copy data from src to dest and swap if indicated. The value of arr is only used for flexible ( `NPY_STRING`, `NPY_UNICODE`, and `NPY_VOID` ) arrays (and is obtained from `arr->descr->elsize` ). The second function copies a single value, while the first loops over n values with the provided strides. These functions can deal with misbehaved src data. If src is NULL then no copy is performed. If swap is 0, then no byteswapping occurs. It is assumed that dest and src do not overlap. If they overlap, then use `memmove` (…) first followed by `copyswap(n)` with NULL valued `src`.

  int compare(const void *d1, const void *d2, void *arr)

    A pointer to a function that compares two elements of the array, `arr`, pointed to by `d1` and `d2`. This function requires behaved (aligned and not swapped) arrays. The return value is 1 if * `d1` > * `d2`, 0 if * `d1` == * `d2`, and -1 if * `d1` < * `d2`. The array object `arr` is used to retrieve itemsize and field information for flexible arrays.

  int argmax(void *data, npy_intp n, npy_intp *max_ind, void *arr)

    A pointer to a function that retrieves the index of the largest of `n` elements in `arr` beginning at the element pointed to by `data`. This function requires that the memory segment be contiguous and behaved. The return value is always 0. The index of the largest element is returned in `max_ind`.

  void dotfunc(void *ip1, npy_intp is1, void *ip2, npy_intp is2, void *op, npy_intp n, void *arr)

    A pointer to a function that multiplies two `n` -length sequences together, adds them, and places the result in element pointed to by `op` of `arr`. The start of the two sequences are pointed to by `ip1` and `ip2`. To get to the next element in each sequence requires a jump of `is1` and `is2` bytes, respectively. This function requires behaved (though not necessarily contiguous) memory.

  int scanfunc(FILE *fd, void *ip, void *arr)

    A pointer to a function that scans (scanf style) one element of the corresponding type from the file descriptor `fd` into the array memory pointed to by `ip`. The array is assumed to be behaved. The last argument `arr` is the array to be scanned into. Returns number of receiving arguments successfully assigned (which may be zero in case a matching failure occurred before the first receiving argument was assigned), or EOF if input failure occurs before the first receiving argument was assigned. This function should be called without holding the Python GIL, and has to grab it for error reporting.

  int fromstr(char *str, void *ip, char **endptr, void *arr)

    A pointer to a function that converts the string pointed to by `str` to one element of the corresponding type and places it in the memory location pointed to by `ip`. After the conversion is completed, `*endptr` points to the rest of the string. The last argument `arr` is the array into which ip points (needed for variable-size data- types). Returns 0 on success or -1 on failure. Requires a behaved array. This function should be called without holding the Python GIL, and has to grab it for error reporting.

  npy_bool nonzero(void *data, void *arr)

    A pointer to a function that returns TRUE if the item of `arr` pointed to by `data` is nonzero. This function can deal with misbehaved arrays.

  void fill(void *data, npy_intp length, void *arr)

    A pointer to a function that fills a contiguous array of given length with data. The first two elements of the array must already be filled- in. From these two values, a delta will be computed and the values from item 3 to the end will be computed by repeatedly adding this computed delta. The data buffer must be well-behaved.

  void fillwithscalar(void *buffer, npy_intp length, void *value, void *arr)

    A pointer to a function that fills a contiguous `buffer` of the given `length` with a single scalar `value` whose address is given. The final argument is the array which is needed to get the itemsize for variable-length arrays.

  int sort(void *start, npy_intp length, void *arr)

    An array of function pointers to a particular sorting algorithms. A particular sorting algorithm is obtained using a key (so far `NPY_QUICKSORT`, `NPY_HEAPSORT`, and `NPY_MERGESORT` are defined). These sorts are done in-place assuming contiguous and aligned data.

  int argsort(void *start, npy_intp *result, npy_intp length, void *arr)

    An array of function pointers to sorting algorithms for this data type. The same sorting algorithms as for sort are available. The indices producing the sort are returned in `result` (which must be initialized with indices 0 to `length-1` inclusive).

  PyObject *castdict

    Either `NULL` or a dictionary containing low-level casting functions for user- defined data-types. Each function is wrapped in a PyCapsule* and keyed by the data-type number.

  NPY_SCALARKIND scalarkind(PyArrayObject *arr)

    A function to determine how scalars of this type should be interpreted. The argument is `NULL` or a 0-dimensional array containing the data (if that is needed to determine the kind of scalar). The return value must be of type `NPY_SCALARKIND`.

  int **cancastscalarkindto

    Either `NULL` or an array of `NPY_NSCALARKINDS` pointers. These pointers should each be either `NULL` or a pointer to an array of integers (terminated by `NPY_NOTYPE`) indicating data-types that a scalar of this data-type of the specified kind can be cast to safely (this usually means without losing precision).

  int *cancastto

    Either `NULL` or an array of integers (terminated by `NPY_NOTYPE` ) indicated data-types that this data-type can be cast to safely (this usually means without losing precision).

  int argmin(void *data, npy_intp n, npy_intp *min_ind, void *arr)

    A pointer to a function that retrieves the index of the smallest of `n` elements in `arr` beginning at the element pointed to by `data`. This function requires that the memory segment be contiguous and behaved. The return value is always 0. The index of the smallest element is returned in `min_ind`.

### PyArrayMethod_Context and PyArrayMethod_Spec

type PyArrayMethodObject_tag

  An opaque struct used to represent the method “self” in ArrayMethod loops.

type PyArrayMethod_Context

  A struct that is passed in to ArrayMethod loops to provide context for the runtime usage of the loop.

      typedef struct {
          PyObject *caller;
          struct PyArrayMethodObject_tag *method;
          PyArray_Descr *const *descriptors;
          void *parameters;
      } PyArrayMethod_Context

  PyObject *caller

    The caller, which is typically the ufunc that called the loop. May be `NULL` when a call is not from a ufunc (e.g. casts).

  struct PyArrayMethodObject_tag *method

    The method “self”. Currently this object is an opaque pointer.

  PyArray_Descr **descriptors

    An array of descriptors for the ufunc loop, filled in by `resolve_descriptors`. The length of the array is `nin` + `nout`.

  void *parameters

    > A pointer to a structure containing any runtime parameters needed by the loop. This is `NULL` if no parameters are needed. The type of the struct is specific to the registered function.

    Changed in version NumPy: 2.4 The parameters member was added in NumPy 2.4.

type PyArrayMethod_Spec

  A struct used to register an ArrayMethod with NumPy. We use the slots mechanism used by the Python limited API. See below for the slot definitions.

      typedef struct {
         const char *name;
         int nin, nout;
         NPY_CASTING casting;
         NPY_ARRAYMETHOD_FLAGS flags;
         PyArray_DTypeMeta **dtypes;
         PyType_Slot *slots;
      } PyArrayMethod_Spec;

  const char *name

    The name of the loop.

  int nin

    The number of input operands

  int nout

    The number of output operands.

  NPY_CASTING casting

    Used to indicate how minimally permissive a casting operation should be. For example, if a cast operation might in some circumstances be safe, but in others unsafe, then `NPY_UNSAFE_CASTING` should be set. Not used for ufunc loops but must still be set.

  NPY_ARRAYMETHOD_FLAGS flags

    The flags set for the method.

  PyArray_DTypeMeta **dtypes

    The DTypes for the loop. Must be `nin` + `nout` in length.

  PyType_Slot *slots

    An array of slots for the method. Slot IDs must be one of the values below.

### PyArray_DTypeMeta and PyArrayDTypeMeta_Spec

PyTypeObject PyArrayDTypeMeta_Type

  The python type object corresponding to `PyArray_DTypeMeta`.

type PyArray_DTypeMeta

  A largely opaque struct representing DType classes. Each instance defines a metaclass for a single NumPy data type. Data types can either be non-parametric or parametric. For non-parametric types, the DType class has a one-to-one correspondence with the descriptor instance created from the DType class. Parametric types can correspond to many different dtype instances depending on the chosen parameters. This type is available in the public `numpy/dtype_api.h` header. Currently use of this struct is not supported in the limited CPython API, so if `Py_LIMITED_API` is set, this type is a typedef for `PyTypeObject`.

      typedef struct {
           PyHeapTypeObject super;
           PyArray_Descr *singleton;
           int type_num;
           PyTypeObject *scalar_type;
           npy_uint64 flags;
           void *dt_slots;
           void *reserved[3];
      } PyArray_DTypeMeta

  PyHeapTypeObject super

    The superclass, providing hooks into the python object API. Set members of this struct to fill in the functions implementing the `PyTypeObject` API (e.g. `tp_new`).

  PyArray_Descr *singleton

    A descriptor instance suitable for use as a singleton descriptor for the data type. This is useful for non-parametric types representing simple plain old data type where there is only one logical descriptor instance for all data of the type. Can be NULL if a singleton instance is not appropriate.

  int type_num

    Corresponds to the type number for legacy data types. Data types defined outside of NumPy and possibly future data types shipped with NumPy will have `type_num` set to -1, so this should not be relied on to discriminate between data types.

  PyTypeObject *scalar_type

    The type of scalar instances for this data type.

  npy_uint64 flags

    Flags can be set to indicate to NumPy that this data type has optional behavior. See Flags for a listing of allowed flag values.

  void *dt_slots

    An opaque pointer to a private struct containing implementations of functions in the DType API. This is filled in from the `slots` member of the `PyArrayDTypeMeta_Spec` instance used to initialize the DType.

type PyArrayDTypeMeta_Spec

  A struct used to initialize a new DType with the `PyArrayInitDTypeMeta_FromSpec` function.

      typedef struct {
          PyTypeObject *typeobj;
          int flags;
          PyArrayMethod_Spec **casts;
          PyType_Slot *slots;
          PyTypeObject *baseclass;
      }

  PyTypeObject *typeobj

    Either `NULL` or the type of the python scalar associated with the DType. Scalar indexing into an array returns an item with this type.

  int flags

    Static flags for the DType class, indicating whether the DType is parametric, abstract, or represents numeric data. The latter is optional but is useful to set to indicate to downstream code if the DType represents data that are numbers (ints, floats, or other numeric data type) or something else (e.g. a string, unit, or date).

  PyArrayMethod_Spec **casts;

    A `NULL`-terminated array of ArrayMethod specifications for casts defined by the DType.

  PyType_Slot *slots;

    A `NULL`-terminated array of slot specifications for implementations of functions in the DType API. Slot IDs must be one of the DType slot IDs enumerated in Slot IDs and API Function Typedefs.

### Exposed DTypes classes (`PyArray_DTypeMeta` objects)

For use with promoters, NumPy exposes a number of Dtypes following the pattern `PyArray_<Name>DType` corresponding to those found in np.dtypes.

Additionally, the three DTypes, `PyArray_PyLongDType`, `PyArray_PyFloatDType`, `PyArray_PyComplexDType` correspond to the Python scalar values. These cannot be used in all places, but do allow for example the common dtype operation and implementing promotion with them may be necessary.

Further, the following abstract DTypes are defined which cover both the builtin NumPy ones and the python ones, and users can in principle subclass from them (this does not inherit any DType specific functionality): * `PyArray_IntAbstractDType` * `PyArray_FloatAbstractDType` * `PyArray_ComplexAbstractDType`

Warning

As of NumPy 2.0, the only valid use for these DTypes is registering a promoter conveniently to e.g. match “any integers” (and subclass checks). Because of this, they are not exposed to Python.

### PyUFunc_Type and PyUFuncObject

PyTypeObject PyUFunc_Type

  The ufunc object is implemented by creation of the `PyUFunc_Type`. It is a very simple type that implements only basic getattribute behavior, printing behavior, and has call behavior which allows these objects to act like functions. The basic idea behind the ufunc is to hold a reference to fast 1-dimensional (vector) loops for each data type that supports the operation. These one-dimensional loops all have the same signature and are the key to creating a new ufunc. They are called by the generic looping code as appropriate to implement the N-dimensional function. There are also some generic 1-d loops defined for floating and complexfloating arrays that allow you to define a ufunc using a single scalar function (e.g. atanh).

type PyUFuncObject

  The core of the ufunc is the `PyUFuncObject` which contains all the information needed to call the underlying C-code loops that perform the actual work. While it is described here for completeness, it should be considered internal to NumPy and manipulated via `PyUFunc_*` functions. The size of this structure is subject to change across versions of NumPy. To ensure compatibility:

  - Never declare a non-pointer instance of the struct

  - Never perform pointer arithmetic

  - Never use `sizeof(PyUFuncObject)`

  It has the following structure:

      typedef struct {
          PyObject_HEAD
          int nin;
          int nout;
          int nargs;
          int identity;
          PyUFuncGenericFunction *functions;
          void **data;
          int ntypes;
          int reserved1;
          const char *name;
          char *types;
          const char *doc;
          void *ptr;
          PyObject *obj;
          PyObject *userloops;
          int core_enabled;
          int core_num_dim_ix;
          int *core_num_dims;
          int *core_dim_ixs;
          int *core_offsets;
          char *core_signature;
          PyUFunc_TypeResolutionFunc *type_resolver;
          void *reserved2;
          void *reserved3;
          npy_uint32 *op_flags;
          npy_uint32 *iter_flags;
          /* new in API version 0x0000000D */
          npy_intp *core_dim_sizes;
          npy_uint32 *core_dim_flags;
          PyObject *identity_value;
          /* Further private slots (size depends on the NumPy version) */
      } PyUFuncObject;

  int nin

    The number of input arguments.

  int nout

    The number of output arguments.

  int nargs

    The total number of arguments (nin + nout). This must be less than `NPY_MAXARGS`.

  int identity

    Either `PyUFunc_One`, `PyUFunc_Zero`, `PyUFunc_MinusOne`, `PyUFunc_None`, `PyUFunc_ReorderableNone`, or `PyUFunc_IdentityValue` to indicate the identity for this operation. It is only used for a reduce-like call on an empty array.

  void functions(char **args, npy_intp *dims, npy_intp *steps, void *extradata)

    An array of function pointers — one for each data type supported by the ufunc. This is the vector loop that is called to implement the underlying function dims [0] times. The first argument, args, is an array of nargs pointers to behaved memory. Pointers to the data for the input arguments are first, followed by the pointers to the data for the output arguments. How many bytes must be skipped to get to the next element in the sequence is specified by the corresponding entry in the steps array. The last argument allows the loop to receive extra information. This is commonly used so that a single, generic vector loop can be used for multiple functions. In this case, the actual scalar function to call is passed in as extradata. The size of this function pointer array is ntypes.

  void **data

    Extra data to be passed to the 1-d vector loops or `NULL` if no extra-data is needed. This C-array must be the same size ( i.e. ntypes) as the functions array. `NULL` is used if extra_data is not needed. Several C-API calls for UFuncs are just 1-d vector loops that make use of this extra data to receive a pointer to the actual function to call.

  int ntypes

    The number of supported data types for the ufunc. This number specifies how many different 1-d loops (of the builtin data types) are available.

  char *name

    A string name for the ufunc. This is used dynamically to build the __doc__ attribute of ufuncs.

  char *types

    An array of \(nargs \times ntypes\) 8-bit type_numbers which contains the type signature for the function for each of the supported (builtin) data types. For each of the ntypes functions, the corresponding set of type numbers in this array shows how the args argument should be interpreted in the 1-d vector loop. These type numbers do not have to be the same type and mixed-type ufuncs are supported.

  char *doc

    Documentation for the ufunc. Should not contain the function signature as this is generated dynamically when __doc__ is retrieved.

  void *ptr

    Any dynamically allocated memory. Currently, this is used for dynamic ufuncs created from a python function to store room for the types, data, and name members.

  PyObject *obj

    For ufuncs dynamically created from python functions, this member holds a reference to the underlying Python function.

  PyObject *userloops

    A dictionary of user-defined 1-d vector loops (stored as CObject ptrs) for user-defined types. A loop may be registered by the user for any user-defined type. It is retrieved by type number. User defined type numbers are always larger than `NPY_USERDEF`.

  int core_enabled

    0 for scalar ufuncs; 1 for generalized ufuncs

  int core_num_dim_ix

    Number of distinct core dimension names in the signature

  int *core_num_dims

    Number of core dimensions of each argument

  int *core_dim_ixs

    Dimension indices in a flattened form; indices of argument `k` are stored in `core_dim_ixs[core_offsets[k] : core_offsets[k] + core_numdims[k]]`

  int *core_offsets

    Position of 1st core dimension of each argument in `core_dim_ixs`, equivalent to cumsum(`core_num_dims`)

  char *core_signature

    Core signature string

  PyUFunc_TypeResolutionFunc *type_resolver

    A function which resolves the types and fills an array with the dtypes for the inputs and outputs

    type PyUFunc_TypeResolutionFunc

      The function pointer type for `type_resolver`

  npy_uint32 op_flags

    Override the default operand flags for each ufunc operand.

  npy_uint32 iter_flags

    Override the default nditer flags for the ufunc.

  Added in API version 0x0000000D

  npy_intp *core_dim_sizes

    For each distinct core dimension, the possible frozen size if `UFUNC_CORE_DIM_SIZE_INFERRED` is `0`

  npy_uint32 *core_dim_flags

    For each distinct core dimension, a set of flags ( `UFUNC_CORE_DIM_CAN_IGNORE` and `UFUNC_CORE_DIM_SIZE_INFERRED`)

  PyObject *identity_value

    Identity for reduction, when `PyUFuncObject.identity` is equal to `PyUFunc_IdentityValue`.

UFUNC_CORE_DIM_CAN_IGNORE

  if the dim name ends in `?`

UFUNC_CORE_DIM_SIZE_INFERRED

  if the dim size will be determined from the operands and not from a frozen signature

### PyArrayIter_Type and PyArrayIterObject

PyTypeObject PyArrayIter_Type

  This is an iterator object that makes it easy to loop over an N-dimensional array. It is the object returned from the flat attribute of an ndarray. It is also used extensively throughout the implementation internals to loop over an N-dimensional array. The tp_as_mapping interface is implemented so that the iterator object can be indexed (using 1-d indexing), and a few methods are implemented through the tp_methods table. This object implements the next method and can be used anywhere an iterator can be used in Python.

type PyArrayIterObject

  The C-structure corresponding to an object of `PyArrayIter_Type` is the `PyArrayIterObject`. The `PyArrayIterObject` is used to keep track of a pointer into an N-dimensional array. It contains associated information used to quickly march through the array. The pointer can be adjusted in three basic ways: 1) advance to the “next” position in the array in a C-style contiguous fashion, 2) advance to an arbitrary N-dimensional coordinate in the array, and 3) advance to an arbitrary one-dimensional index into the array. The members of the `PyArrayIterObject` structure are used in these calculations. Iterator objects keep their own dimension and strides information about an array. This can be adjusted as needed for “broadcasting,” or to loop over only specific dimensions.

      typedef struct {
          PyObject_HEAD
          int   nd_m1;
          npy_intp  index;
          npy_intp  size;
          npy_intp  coordinates[NPY_MAXDIMS_LEGACY_ITERS];
          npy_intp  dims_m1[NPY_MAXDIMS_LEGACY_ITERS];
          npy_intp  strides[NPY_MAXDIMS_LEGACY_ITERS];
          npy_intp  backstrides[NPY_MAXDIMS_LEGACY_ITERS];
          npy_intp  factors[NPY_MAXDIMS_LEGACY_ITERS];
          PyArrayObject *ao;
          char  *dataptr;
          npy_bool  contiguous;
      } PyArrayIterObject;

  int nd_m1

    \(N-1\) where \(N\) is the number of dimensions in the underlying array.

  npy_intp index

    The current 1-d index into the array.

  npy_intp size

    The total size of the underlying array.

  npy_intp *coordinates

    An \(N\) -dimensional index into the array.

  npy_intp *dims_m1

    The size of the array minus 1 in each dimension.

  npy_intp *strides

    The strides of the array. How many bytes needed to jump to the next element in each dimension.

  npy_intp *backstrides

    How many bytes needed to jump from the end of a dimension back to its beginning. Note that `backstrides[k] == strides[k] * dims_m1[k]`, but it is stored here as an optimization.

  npy_intp *factors

    This array is used in computing an N-d index from a 1-d index. It contains needed products of the dimensions.

  PyArrayObject *ao

    A pointer to the underlying ndarray this iterator was created to represent.

  char *dataptr

    This member points to an element in the ndarray indicated by the index.

  npy_bool contiguous

    This flag is true if the underlying array is `NPY_ARRAY_C_CONTIGUOUS`. It is used to simplify calculations when possible.

How to use an array iterator on a C-level is explained more fully in later sections. Typically, you do not need to concern yourself with the internal structure of the iterator object, and merely interact with it through the use of the macros `PyArray_ITER_NEXT` (it), `PyArray_ITER_GOTO` (it, dest), or `PyArray_ITER_GOTO1D` (it, index). All of these macros require the argument it to be a PyArrayIterObject*.

### PyArrayMultiIter_Type and PyArrayMultiIterObject

PyTypeObject PyArrayMultiIter_Type

  This type provides an iterator that encapsulates the concept of broadcasting. It allows \(N\) arrays to be broadcast together so that the loop progresses in C-style contiguous fashion over the broadcasted array. The corresponding C-structure is the `PyArrayMultiIterObject` whose memory layout must begin any object, obj, passed in to the `PyArray_Broadcast` (obj) function. Broadcasting is performed by adjusting array iterators so that each iterator represents the broadcasted shape and size, but has its strides adjusted so that the correct element from the array is used at each iteration.

type PyArrayMultiIterObject

      typedef struct {
          PyObject_HEAD
          int numiter;
          npy_intp size;
          npy_intp index;
          int nd;
          npy_intp dimensions[NPY_MAXDIMS_LEGACY_ITERS];
          PyArrayIterObject *iters[];
      } PyArrayMultiIterObject;

  int numiter

    The number of arrays that need to be broadcast to the same shape.

  npy_intp size

    The total broadcasted size.

  npy_intp index

    The current (1-d) index into the broadcasted result.

  int nd

    The number of dimensions in the broadcasted result.

  npy_intp *dimensions

    The shape of the broadcasted result (only `nd` slots are used).

  PyArrayIterObject **iters

    An array of iterator objects that holds the iterators for the arrays to be broadcast together. On return, the iterators are adjusted for broadcasting.

### PyArrayNeighborhoodIter_Type and PyArrayNeighborhoodIterObject

PyTypeObject PyArrayNeighborhoodIter_Type

  This is an iterator object that makes it easy to loop over an N-dimensional neighborhood.

type PyArrayNeighborhoodIterObject

  The C-structure corresponding to an object of `PyArrayNeighborhoodIter_Type` is the `PyArrayNeighborhoodIterObject`.

      typedef struct {
          PyObject_HEAD
          int nd_m1;
          npy_intp index, size;
          npy_intp coordinates[NPY_MAXDIMS_LEGACY_ITERS]
          npy_intp dims_m1[NPY_MAXDIMS_LEGACY_ITERS];
          npy_intp strides[NPY_MAXDIMS_LEGACY_ITERS];
          npy_intp backstrides[NPY_MAXDIMS_LEGACY_ITERS];
          npy_intp factors[NPY_MAXDIMS_LEGACY_ITERS];
          PyArrayObject *ao;
          char *dataptr;
          npy_bool contiguous;
          npy_intp bounds[NPY_MAXDIMS_LEGACY_ITERS][2];
          npy_intp limits[NPY_MAXDIMS_LEGACY_ITERS][2];
          npy_intp limits_sizes[NPY_MAXDIMS_LEGACY_ITERS];
          npy_iter_get_dataptr_t translate;
          npy_intp nd;
          npy_intp dimensions[NPY_MAXDIMS_LEGACY_ITERS];
          PyArrayIterObject* _internal_iter;
          char* constant;
          int mode;
      } PyArrayNeighborhoodIterObject;

### ScalarArrayTypes

There is a Python type for each of the different built-in data types that can be present in the array. Most of these are simple wrappers around the corresponding data type in C. The C-names for these types are `Py{TYPE}ArrType_Type` where `{TYPE}` can be

> Bool, Byte, Short, Int, Long, LongLong, UByte, UShort, UInt, ULong, ULongLong, Half, Float, Double, LongDouble, CFloat, CDouble, CLongDouble, String, Unicode, Void, Datetime, Timedelta, and Object.

These type names are part of the C-API and can therefore be created in extension C-code. There is also a `PyIntpArrType_Type` and a `PyUIntpArrType_Type` that are simple substitutes for one of the integer types that can hold a pointer on the platform. The structure of these scalar objects is not exposed to C-code. The function `PyArray_ScalarAsCtype` (..) can be used to extract the C-type value from the array scalar and the function `PyArray_Scalar` (…) can be used to construct an array scalar from a C-value.

## Other C-structures

A few new C-structures were found to be useful in the development of NumPy. These C-structures are used in at least one C-API call and are therefore documented here. The main reason these structures were defined is to make it easy to use the Python ParseTuple C-API to convert from Python objects to a useful C-Object.

### PyArray_Dims

type PyArray_Dims

  This structure is very useful when shape and/or strides information is supposed to be interpreted. The structure is:

      typedef struct {
          npy_intp *ptr;
          int len;
      } PyArray_Dims;

  The members of this structure are

  npy_intp *ptr

    A pointer to a list of (`npy_intp`) integers which usually represent array shape or array strides.

  int len

    The length of the list of integers. It is assumed safe to access ptr [0] to ptr [len-1].

### PyArray_Chunk

type PyArray_Chunk

  This is equivalent to the buffer object structure in Python up to the ptr member. On 32-bit platforms (i.e. if `NPY_SIZEOF_INT` == `NPY_SIZEOF_INTP`), the len member also matches an equivalent member of the buffer object. It is useful to represent a generic single-segment chunk of memory.

      typedef struct {
          PyObject_HEAD
          PyObject *base;
          void *ptr;
          npy_intp len;
          int flags;
      } PyArray_Chunk;

  The members are

  PyObject *base

    The Python object this chunk of memory comes from. Needed so that memory can be accounted for properly.

  void *ptr

    A pointer to the start of the single-segment chunk of memory.

  npy_intp len

    The length of the segment in bytes.

  int flags

    Any data flags (e.g. `NPY_ARRAY_WRITEABLE` ) that should be used to interpret the memory.

### PyArrayInterface

See also

The array interface protocol

type PyArrayInterface

  The `PyArrayInterface` structure is defined so that NumPy and other extension modules can use the rapid array interface protocol. The `__array_struct__` method of an object that supports the rapid array interface protocol should return a `PyCapsule` that contains a pointer to a `PyArrayInterface` structure with the relevant details of the array. After the new array is created, the attribute should be `DECREF`’d which will free the `PyArrayInterface` structure. Remember to `INCREF` the object (whose `__array_struct__` attribute was retrieved) and point the base member of the new `PyArrayObject` to this same object. In this way the memory for the array will be managed correctly.

      typedef struct {
          int two;
          int nd;
          char typekind;
          int itemsize;
          int flags;
          npy_intp *shape;
          npy_intp *strides;
          void *data;
          PyObject *descr;
      } PyArrayInterface;

  int two

    the integer 2 as a sanity check.

  int nd

    the number of dimensions in the array.

  char typekind

    A character indicating what kind of array is present according to the typestring convention with ‘t’ -> bitfield, ‘b’ -> Boolean, ‘i’ -> signed integer, ‘u’ -> unsigned integer, ‘f’ -> floating point, ‘c’ -> complex floating point, ‘O’ -> object, ‘S’ -> (byte-)string, ‘U’ -> unicode, ‘V’ -> void.

  int itemsize

    The number of bytes each item in the array requires.

  int flags

    Any of the bits `NPY_ARRAY_C_CONTIGUOUS` (1), `NPY_ARRAY_F_CONTIGUOUS` (2), `NPY_ARRAY_ALIGNED` (0x100), `NPY_ARRAY_NOTSWAPPED` (0x200), or `NPY_ARRAY_WRITEABLE` (0x400) to indicate something about the data. The `NPY_ARRAY_ALIGNED`, `NPY_ARRAY_C_CONTIGUOUS`, and `NPY_ARRAY_F_CONTIGUOUS` flags can actually be determined from the other parameters. The flag `NPY_ARR_HAS_DESCR` (0x800) can also be set to indicate to objects consuming the version 3 array interface that the descr member of the structure is present (it will be ignored by objects consuming version 2 of the array interface).

  npy_intp *shape

    An array containing the size of the array in each dimension.

  npy_intp *strides

    An array containing the number of bytes to jump to get to the next element in each dimension.

  void *data

    A pointer to the first element of the array.

  PyObject *descr

    A Python object describing the data-type in more detail (same as the descr key in `__array_interface__`). This can be `NULL` if typekind and itemsize provide enough information. This field is also ignored unless `NPY_ARR_HAS_DESCR` flag is on in flags.

### Internally used structures

Internally, the code uses some additional Python objects primarily for memory management. These types are not accessible directly from Python, and are not exposed to the C-API. They are included here only for completeness and assistance in understanding the code.

type PyUFunc_Loop1d

  A simple linked-list of C-structures containing the information needed to define a 1-d loop for a ufunc for every defined signature of a user-defined data-type.

PyTypeObject PyArrayMapIter_Type

  Advanced indexing is handled with this Python type. It is simply a loose wrapper around the C-structure containing the variables needed for advanced array indexing.

type PyArrayMapIterObject

  The C-structure associated with `PyArrayMapIter_Type`. This structure is useful if you are trying to understand the advanced-index mapping code. It is defined in the `multiarray/mapping.h` header. This type is not exposed to Python and could be replaced with a C-structure. As a Python type it takes advantage of reference- counted memory management.

## NumPy C-API and C complex

When you use the NumPy C-API, you will have access to complex real declarations `npy_cdouble` and `npy_cfloat`, which are declared in terms of the C standard types from `complex.h`. Unfortunately, `complex.h` contains `#define I ...` (where the actual definition depends on the compiler), which means that any downstream user that does `#include <numpy/arrayobject.h>` could get `I` defined, and using something like declaring `double I;` in their code will result in an obscure compiler error like

This error can be avoided by adding:

    #undef I

to your code.

Changed in version 2.0: The inclusion of `complex.h` was new in NumPy 2, so that code defining a different `I` may not have required the `#undef I` on older versions. NumPy 2.0.1 briefly included the `#under I`