Message 92175 - Python tracker

➜

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	loewis
Recipients	amaury.forgeotdarc, barry, benjamin.peterson, boya, donmez, gpolo, lemburg, loewis, pitrou, teoliphant
Date	2009年09月02日.18:45:10
SpamBayes Score	0.00095202285
Marked as misclassified	No
Message-id	<4A9EBD34.6010305@v.loewis.de>
In-reply-to	<1251903686.64.0.849841495659.issue3139@psf.upfronthosting.co.za>

Content
A problem can only occur if you preserve a pointer to the buffer, and the object gets a chance to change its buffer underneath. This can happen when there are user-defined callback, and when other threads can get control. In the cases being fixed, other threads can get control, as the GIL is released. In the cases you discuss, this cannot happen, since the GIL is not released, and no codepath can lead to buffer reallocation.

Content

A problem can only occur if you preserve a pointer to the buffer,
and the object gets a chance to change its buffer underneath. This
can happen when there are user-defined callback, and when other
threads can get control. In the cases being fixed, other threads
*can* get control, as the GIL is released. In the cases you discuss,
this cannot happen, since the GIL is not released, and no codepath
can lead to buffer reallocation.

History
Date	User	Action	Args
2009年09月02日 18:45:12	loewis	set	recipients: + loewis, lemburg, barry, teoliphant, amaury.forgeotdarc, pitrou, donmez, benjamin.peterson, gpolo, boya
2009年09月02日 18:45:10	loewis	link	issue3139 messages
2009年09月02日 18:45:10	loewis	create

homepage