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 teoliphant
Recipients scoder, teoliphant
Date 2008-06-06.16:24:15
SpamBayes Score 0.27524424
Marked as misclassified No
Message-id <1212769458.44.0.925537626531.issue3046@psf.upfronthosting.co.za>
In-reply-to
Content
Greg Ewing's comment in the thread that read/write locking is orthogonal
to memory-buffer moving is to me the most convincing argument that the
locking portion of the getbuffer function call should be removed and
potentially placed in a separate API at some point.   This will simplify
the protocol a bit.  

I will apply the patch.
History
Date User Action Args
2008-06-06 16:24:18teoliphantsetspambayes_score: 0.275244 -> 0.27524424
recipients: + teoliphant, scoder
2008-06-06 16:24:18teoliphantsetspambayes_score: 0.275244 -> 0.275244
messageid: <1212769458.44.0.925537626531.issue3046@psf.upfronthosting.co.za>
2008-06-06 16:24:17teoliphantlinkissue3046 messages
2008-06-06 16:24:16teoliphantcreate