FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

gh-148431: Clarify format and item size in buffer requests by limadog9 · Pull Request #159832 · python/cpython · GitHub

  1. python
  2. cpython

Repository navigation

gh-148431: Clarify format and item size in buffer requests #159832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
limadog9 wants to merge 1 commit into
base: main
Choose a base branch
Could not load branches
Branch not found: {{ refName }}

Are you sure you want to change the base?

Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
from
+12 −5
Conversation 1 Commits 1 Checks 32 Files changed 1
Open

gh-148431: Clarify format and item size in buffer requests #159832

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension .rst  (1) All 1 file type selected
Viewed files
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Unified
Split
Hide whitespace
Diff view
Unified
Split
Hide whitespace
17 changes: 12 additions & 5 deletions Doc/c-api/buffer.rst
Show comments
View file
Open in desktop
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Show hidden characters
Original file line number Diff line number Diff line change
Expand Up @@ -151,8 +151,12 @@ a buffer, see :c:func:`PyObject_GetBuffer`.
.. c:member:: char *format

A *NULL* terminated string in :mod:`struct` module style syntax describing
the contents of a single item. If this is ``NULL``, ``"B"`` (unsigned bytes)
is assumed.
the contents of a single item. If this is ``NULL``, the original format
is not available to the consumer. For a :c:macro:`PyBUF_SIMPLE` or
:c:macro:`PyBUF_WRITABLE` request, the buffer is treated as unsigned bytes
(``"B"``). For other requests without :c:macro:`PyBUF_FORMAT`,
:c:member:`~Py_buffer.itemsize` still describes the size of each item,
even though its format is unknown.

This field is controlled by the :c:macro:`PyBUF_FORMAT` flag.

Expand Down Expand Up @@ -272,9 +276,12 @@ readonly, format
Since :c:macro:`PyBUF_SIMPLE` is defined as 0, :c:macro:`PyBUF_WRITABLE`
can be used as a stand-alone flag to request a simple writable buffer.

:c:macro:`PyBUF_FORMAT` must be \|'d to any of the flags except :c:macro:`PyBUF_SIMPLE`, because
the latter already implies format ``B`` (unsigned bytes). :c:macro:`!PyBUF_FORMAT` cannot be
used on its own.
:c:macro:`PyBUF_FORMAT` is optional and can be \|'d to any of the flags in the
next section except :c:macro:`PyBUF_SIMPLE`. Without it, the exporter sets
:c:member:`~Py_buffer.format` to ``NULL``, even when shape information is
requested. To request the original format, combine :c:macro:`!PyBUF_FORMAT`
with :c:macro:`PyBUF_ND` or a flag that includes it. It cannot be used on its
own or combined only with :c:macro:`PyBUF_WRITABLE`.


shape, strides, suboffsets
Expand Down
Loading
Back | FazBrowse Home | New Git URL