Message125636
| Author | ncoghlan |
|---|---|
| Recipients | kermode, mark.dickinson, ncoghlan, pitrou, teoliphant |
| Date | 2011-01-07.09:39:47 |
| SpamBayes Score | 4.825724e-07 |
| Marked as misclassified | No |
| Message-id | <1294393189.36.0.314965457582.issue9990@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
As per the discussion over in issue #10181, I've changed my position on this issue. Since the PEP isn't explicit on the exact semantics here, I think we should be guided by the memoryview behaviour and make it official that bf_releasebuffer implementations shouldn't trust the contents of the passed in Py_buffer struct. Instead, if that information is important, the exporter should create an internal data structure that preserves the necessary detail and merely use the Py_buffer address as an identifier to locate the internal copy. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-07 09:39:49 | ncoghlan | set | recipients: + ncoghlan, teoliphant, mark.dickinson, kermode, pitrou |
| 2011-01-07 09:39:49 | ncoghlan | set | messageid: <1294393189.36.0.314965457582.issue9990@psf.upfronthosting.co.za> |
| 2011-01-07 09:39:47 | ncoghlan | link | issue9990 messages |
| 2011-01-07 09:39:47 | ncoghlan | create | |