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-28.18:47:36
SpamBayes Score 0.30711767
Marked as misclassified No
Message-id <1206730057.92.0.69403563693.issue815646@psf.upfronthosting.co.za>
In-reply-to
Content
On the other hand, surprisingly enough, the flockfile/funlockfile
manpage tells me that:

       The stdio functions are thread-safe.  This is achieved by 
assigning  to  each  FILE
       object  a  lockcount  and  (if the lockcount is nonzero) an
owning thread.  For each
       library call, these functions wait until the FILE object is no
longer  locked  by  a
       different thread, then lock it, do the requested I/O, and unlock
the object again.

This leaves me wondering what is happening in the above-mentioned test.
History
Date User Action Args
2008-03-28 18:47:38pitrousetspambayes_score: 0.307118 -> 0.30711767
recipients: + pitrou, tim.peters, loewis, jhylton, anthonybaxter, jafo, janixia, christian.heimes
2008-03-28 18:47:38pitrousetspambayes_score: 0.307118 -> 0.307118
messageid: <1206730057.92.0.69403563693.issue815646@psf.upfronthosting.co.za>
2008-03-28 18:47:37pitroulinkissue815646 messages
2008-03-28 18:47:36pitroucreate