Message120281
| Author |
pitrou |
| Recipients |
ncoghlan, pitrou, rupole |
| Date |
2010年11月02日.23:01:11 |
| SpamBayes Score |
4.5930934e-05 |
| Marked as misclassified |
No |
| Message-id |
<1288738868.3541.14.camel@localhost.localdomain> |
| In-reply-to |
<1288738629.35.0.53407341178.issue10181@psf.upfronthosting.co.za> |
| Content |
> Read the "Releasing the buffer" section in PEP 3118 again. Unless I'm
> misunderstanding you completely, the rules you're asking for are
> already in place: those fields are entirely the responsibility of the
> exporting object, and it needs to ensure they remain valid until the
> buffer is released.
In practice, though, we copy Py_buffer structs around and there's no way
for the original object to know about that. That's the fundamental
difference with a PyObject where you would only increase a refcount
instead of copying the structure's contents. |
|