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, donmez, giampaolo.rodola, gpolo, loewis, pitrou, teoliphant
Date 2008-08-01.14:29:07
SpamBayes Score 3.976868e-05
Marked as misclassified No
Message-id <1217600948.6.0.899200568172.issue3139@psf.upfronthosting.co.za>
In-reply-to
Content
Amaury, I think the issue of thread-safety of the io library should be
decoupled from this issue. I don't think it is release-critical that the
io library is thread-safe (and even if it is release-critical, the
problem should be tracked in a different issue, as it requires a
completely independent patch).

The original issue (bytearrays are not thread-safe) will not be
completely resolved (for a certain definition of "thread-safe"): it will
always be possible that one thread observes a locked byte object - this
is by design of the buffer interface, and it is a good design.
History
Date User Action Args
2008-08-01 14:29:08loewissetrecipients: + loewis, barry, teoliphant, amaury.forgeotdarc, pitrou, giampaolo.rodola, donmez, benjamin.peterson, gpolo
2008-08-01 14:29:08loewissetmessageid: <1217600948.6.0.899200568172.issue3139@psf.upfronthosting.co.za>
2008-08-01 14:29:08loewislinkissue3139 messages
2008-08-01 14:29:07loewiscreate