argument, and store in the instance's :c:member:`~PyVarObject.ob_size` field.
Note that the :c:member:`~PyVarObject.ob_size` field may later be used for
other purposes. For example, :py:type:`int` instances use the bits of
- :c:member:`~PyVarObject.ob_size` in an implementation-defined
- way; the underlying storage and its size should be accessed using
- :c:func:`PyLong_Export`.
+ :c:member:`~PyVarObject.ob_size` in an implementation-defined way.
.. note::
steps:
(1) Check if the request can be met. If not, raise :exc:`BufferError`,
- set :c:expr:`view->obj` to ``NULL`` and return ``-1``.
+ set ``view->obj`` to ``NULL`` and return ``-1``.
(2) Fill in the requested fields.
(3) Increment an internal counter for the number of exports.
- (4) Set :c:expr:`view->obj` to *exporter* and increment :c:expr:`view->obj`.
+ (4) Set ``view->obj`` to *exporter* and increment ``view->obj``.
(5) Return ``0``.
schemes can be used:
* Re-export: Each member of the tree acts as the exporting object and
- sets :c:expr:`view->obj` to a new reference to itself.
+ sets ``view->obj`` to a new reference to itself.
* Redirect: The buffer request is redirected to the root object of the
- tree. Here, :c:expr:`view->obj` will be a new reference to the root
+ tree. Here, ``view->obj`` will be a new reference to the root
object.
The individual fields of *view* are described in section
*view* argument.
- This function MUST NOT decrement :c:expr:`view->obj`, since that is
+ This function MUST NOT decrement ``view->obj``, since that is
done automatically in :c:func:`PyBuffer_Release` (this scheme is
useful for breaking reference cycles).
projects / thirdparty / Python / cpython.git / commitdiff
