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 | pitrou |
|---|---|
| Recipients | pitrou |
| Date | 2008年07月05日.22:05:01 |
| SpamBayes Score | 0.00012253091 |
| Marked as misclassified | No |
| Message-id | <1215295503.07.0.531699971785.issue3293@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The declaration for PyObject_ReleaseBuffer (in Include/abstract.h) has the following comments attached to it. But the part about the return value is wrong since the function is defined as returning void. Also, PEP 3118 says it always succeeds so it can't return an error code. By the way, may I suggest that having the buffer API declared in abstract.h but the Py_buffer struct declared in object.h (and why not in bufferobject.h?) is slightly confusing. /* C-API version of the releasebuffer function call. It checks to make sure the object has the required function pointer and issues the call. The obj must have the buffer interface or this function will cause a segfault (i.e. it is assumed to be called only after a corresponding getbuffer which already verified the existence of the tp_as_buffer pointer). Returns 0 on success and -1 (with an error raised) on failure. This function always succeeds (as a NO-OP) if there is no releasebuffer function for the object so that it can always be called when the consumer is done with the buffer */ |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月05日 22:05:03 | pitrou | set | spambayes_score: 0.000122531 -> 0.00012253091 recipients: + pitrou |
| 2008年07月05日 22:05:03 | pitrou | set | spambayes_score: 0.000122531 -> 0.000122531 messageid: <1215295503.07.0.531699971785.issue3293@psf.upfronthosting.co.za> |
| 2008年07月05日 22:05:02 | pitrou | link | issue3293 messages |
| 2008年07月05日 22:05:01 | pitrou | create | |