This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author seberg
Recipients seberg
Date 2020-01-27.22:28:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580164102.73.0.152404784517.issue39471@roundup.psfhosted.org>
In-reply-to
Content
Hmmm, it seems I had missed this chunk of PEP 3118 before:

> Exporters will need to define a bf_releasebuffer function if they can re-allocate their memory, strides, shape, suboffsets, or format variables which they might share through the struct bufferinfo.

Which reads like the opposite of what I would like to see, unfortunately. Which I guess means that the parsing issue should be addressed differently. Opinions still welcome, though.
History
Date User Action Args
2020-01-27 22:28:22sebergsetrecipients: + seberg
2020-01-27 22:28:22sebergsetmessageid: <1580164102.73.0.152404784517.issue39471@roundup.psfhosted.org>
2020-01-27 22:28:22seberglinkissue39471 messages
2020-01-27 22:28:22sebergcreate