[issue595601] file (& socket) I/O are not thread safe

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: Fix committed to trunk in revision 62195 via Issue 815646 Tracker <[EMAIL PROTECTED]> ___

[issue595601] file (& socket) I/O are not thread safe

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- resolution: -> duplicate status: open -> closed superseder: -> thread unsafe file objects cause crash Tracker <[EMAIL PROTECTED]> _

[issue595601] file (& socket) I/O are not thread safe

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: I've posted a preliminary patch for the close()-should-raise-an-error approach here: #815646 -- nosy: +pitrou Tracker <[EMAIL PROTECTED]> _

[issue595601] file (& socket) I/O are not thread safe

Changes by Gregory P. Smith: -- nosy: +gregory.p.smith Tracker <[EMAIL PROTECTED]> ___ Python-bugs-list mailing list Unsubscribe:

[issue595601] file (& socket) I/O are not thread safe

Guido van Rossum added the comment: Given how long this has been sitting without action, it's ludicrous to keep it at "high" priority. I'm also taking it away from Jermy since his interest must be minimal by now. And I'm removing 3.0 since it has a completely different I/O implementation (with

[issue595601] file (& socket) I/O are not thread safe

Christian Heimes added the comment: The race condition issue should get more attention. -- nosy: +tiran priority: normal -> high versions: +Python 2.6, Python 3.0 Tracker <[EMAIL PROTECTED]> __