Author josh.r
Recipients josh.r, serhiy.storchaka
Date 2014-12-06.15:55:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417881328.98.0.646919280576.issue23001@psf.upfronthosting.co.za>
In-reply-to
Content
In the event of calls back into Python code in multithreaded execution (or GIL release), this would mean you no longer have guarantees as to the contents (or even the validity) of the pointer you get back. I'd think the only safe way to accept mutable buffers would be to use the s*, z*, y* codes, which lock the buffer to prevent resize/destruction. Do we want to open segfault vulnerabilities in arbitrary functions?
History
Date User Action Args
2014-12-06 15:55:29josh.rsetrecipients: + josh.r, serhiy.storchaka
2014-12-06 15:55:28josh.rsetmessageid: <1417881328.98.0.646919280576.issue23001@psf.upfronthosting.co.za>
2014-12-06 15:55:28josh.rlinkissue23001 messages
2014-12-06 15:55:28josh.rcreate