Repository navigation
Py_buffer.format declaration inconsistent with the docs #119467
Copy link
Copy link
Closed
Labels
3.12only security fixesonly security fixes3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixesdocsDocumentation in the Doc dirDocumentation in the Doc direasytopic-C-APItype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on May 23, 2024 - addeddocsDocumentation in the Doc dirDocumentation in the Doc dir
on May 23, 2024 Hello!
Would you like to send a PR with fix? :)- added3.12only security fixesonly security fixes3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixes
on May 23, 2024 I'd like to - may take a while...
Reacted by Kirill Podoprigora- added a commit that references this issue
on May 23, 2024 I have pushed a fix for this inconsistency. It would be great if @Eclips4 could review the changes and confirm if this resolves the issue.
Feedback is highly appreciated!
- added a commit that references this issue
on May 23, 2024 - added a commit that references this issue
on May 27, 2024 - marked Py_buffer::format is implemented as
char*instead ofconst char*#94916 as a duplicate of this issueon Nov 9, 2025
Metadata
Metadata
Assignees
Labels
3.12only security fixesonly security fixes3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixesdocsDocumentation in the Doc dirDocumentation in the Doc direasytopic-C-APItype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Bug report
Bug description:
The declaration of the
formatfield of thePy_bufferstructure ischar *but the documentation states it isconst char *.IMHO the declaration should be changed to match the docs.
CPython versions tested on:
3.8, 3.9, 3.10, 3.11, 3.12, 3.13
Operating systems tested on:
Linux, macOS, Windows
Linked PRs