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 anthonybaxter, christian.heimes, jafo, janixia, jhylton, loewis, pitrou, tim.peters
Date 2008-03-29.00:30:32
SpamBayes Score 0.07066038
Marked as misclassified No
Message-id <1206750636.67.0.0119082989476.issue815646@psf.upfronthosting.co.za>
In-reply-to
Content
Some good news: I've found a way to continue with my approach and make
it working. The close() method now raises an appropriate IOError when
another method is being called from another thread. Attaching a patch,
which protects a bunch of file object methods (together with tests). 

Now the bad news: the protection logic in fileobject.c is, hmm, a bit
contrived (and I'm not even sure it's 100% correct). If someone wants to
read it and put his veto before I go further...
History
Date User Action Args
2008-03-29 00:30:37pitrousetspambayes_score: 0.0706604 -> 0.07066038
recipients: + pitrou, tim.peters, loewis, jhylton, anthonybaxter, jafo, janixia, christian.heimes
2008-03-29 00:30:36pitrousetspambayes_score: 0.0706604 -> 0.0706604
messageid: <1206750636.67.0.0119082989476.issue815646@psf.upfronthosting.co.za>
2008-03-29 00:30:35pitroulinkissue815646 messages
2008-03-29 00:30:35pitroucreate