Issue 13860: PyBuffer_FillInfo() return value (original) (raw)

Issue13860

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/58068

classification

Title: PyBuffer_FillInfo() return value
Type: behavior Stage: resolved
Components: Interpreter Core Versions: Python 3.3

process

Status: closed Resolution: duplicate
Dependencies: Superseder: PEP-3118: remove obsolete write-locks View:14203
Assigned To: Nosy List: ncoghlan, pitrou, skrah
Priority: normal Keywords:

Created on 2012-01-25 17:41 by skrah, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (1)
msg151953 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2012-01-25 17:41
This came up in #10419, which is already a little crowded. PyBuffer_FillInfo() returns success if the value for 'view' is NULL. I can't really see a reason for that. Any thoughts?
History
Date User Action Args
2022-04-11 14:57:26 admin set github: 58068
2012-03-06 16:39:42 skrah set superseder: adapt sphinx-quickstart for windows -> PEP-3118: remove obsolete write-locks
2012-03-06 16:39:09 skrah set status: open -> closedresolution: duplicatedependencies: - PEP-3118: remove obsolete write-lockssuperseder: adapt sphinx-quickstart for windowsstage: resolved
2012-03-05 19:24:52 skrah set dependencies: + PEP-3118: remove obsolete write-locks
2012-01-25 17:41:18 skrah create