Author skrah
Recipients jcon, kermode, mark.dickinson, ncoghlan, petri.lehtinen, pitrou, pv, rupole, skrah, teoliphant, vstinner
Date 2011-07-04.10:42:28
SpamBayes Score 4.02758e-11
Marked as misclassified No
Message-id <20110704104022.GA13799@sleipnir.bytereef.org>
In-reply-to <1309222705.19.0.199391578033.issue10181@psf.upfronthosting.co.za>
Content
Nick Coghlan <report@bugs.python.org> wrote:
> The reason redirecting all requests to the underlying object doesn't work
> is because repeated calls to getbuffer on mutable objects are allowed to
> return *different* answers. Assume we have a mutable array type that allows
> changes while memory is exported by keeping the old buffer around until all
> references are released. Then we want the following behaviour:
> 
> The builtin bytearray avoids this issue by simply disallowing mutation while
> a buffer is exported, but memoryview needs to cope with arbitrary third party
> objects which may behave like the hypothetical mutable_byte_array().

I find this behavior quite sane. Would it not be an option to make this
a requirement in the PEP? As far as I can see, Numpy also disallows
mutations on exported buffers.
History
Date User Action Args
2011-07-04 10:42:29skrahsetrecipients: + skrah, teoliphant, mark.dickinson, ncoghlan, rupole, kermode, pitrou, vstinner, pv, jcon, petri.lehtinen
2011-07-04 10:42:28skrahlinkissue10181 messages
2011-07-04 10:42:28skrahcreate