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 pitrou
Recipients amaury.forgeotdarc, benjamin.peterson, loewis, pitrou
Date 2008-08-01.15:55:02
SpamBayes Score 0.005289217
Marked as misclassified No
Message-id <1217606100.489331d4ac51e@imp.free.fr>
In-reply-to <1217605539.5.0.942982690815.issue3476@psf.upfronthosting.co.za>
Content
Hi,

Selon "Martin v. Löwis" <report@bugs.python.org>:
>
> I don't think the proposed patch (file11012) makes it thread-safe, and I
> believe you cannot get it thread-safe without using thread synchronization.

I should have precised that in the context of this issue, "thread-safe" does not
mean "produces perfectly correct output" but simply "does not raise exceptions
when using the same buffered object from two different threads". The former
would be preferable but is not required, IMHO, for a buffered IO library; the
latter is much more critical because as Amaury points out, you otherwise get
exceptions when printing e.g. debut output from multiple threads.
History
Date User Action Args
2008-08-01 15:55:03pitrousetrecipients: + pitrou, loewis, amaury.forgeotdarc, benjamin.peterson
2008-08-01 15:55:03pitroulinkissue3476 messages
2008-08-01 15:55:03pitroucreate