Lines Matching defs:object
2 * Memoryview object implementation
34 The purpose of this object is to facilitate the handling of chained
35 memoryviews that have the same underlying exporting object. PEP-3118
36 allows the underlying object to change while a view is exported. This
41 object, all chained memoryviews use a single buffer snapshot. This
48 base object. shape, strides, suboffsets and format are read-only for
62 exporting base object. In the Python codebase, all getbufferprocs
185 "operation forbidden on released memoryview object"); \
192 "operation forbidden on released memoryview object"); \
782 /* Create a memoryview from an object that implements the buffer protocol.
783 If the object is a memoryview, the new memoryview must be registered
806 "memoryview: a bytes-like object is required, not '%.200s'",
811 /* Copy the format string from a base object that might vanish. */
837 object is NULL, so it does not matter that mbuf_release()
901 Return a new memoryview object based on a contiguous exporter with
914 based on a new bytes object. If order={'C', 'A'ny}, use 'C' order,
945 "for a non-contiguous object.");
960 object: object
962 Create a new memoryview object which references the given object.
966 memoryview_impl(PyTypeObject *type, PyObject *object)
969 return PyMemoryView_FromObject(object);
1062 Release the underlying buffer exposed by the memoryview object.
1360 shape: object = NULL
1430 * object for .release() to work correctly.
1729 /* bytes object */
1887 /* bytes object */
2216 sep: object = NULL
2342 /* Return the item at index. In a one-dimensional view, this is an object
2464 /* mv[obj] returns an object holding the data for one element if obj
2465 fully indexes the memoryview or another memoryview object if it
2758 /* bytes object */
2957 "cannot hash writable memoryview object");
3113 "The underlying object of the memoryview.");