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 davidsarah, georg.brandl, pitrou
Date 2010-08-01.12:23:12
SpamBayes Score 0.00642858
Marked as misclassified No
Message-id <>
The 2.x file object mostly mirrors abilities of the standard C buffered IO functions (including, for example, special behaviour of text files under Windows). Therefore, Python code should call flush() manually if needed. It should be noted that the 2.x file object has been existing for ages and this issue is, to my knowledge, very rarely brought up.

The 3.x IO library should not have this problem since we wrote our own buffering layer, and we have dedicated tests for mixed reads and writes.
Date User Action Args
2010-08-01 12:23:15pitrousetrecipients: + pitrou, georg.brandl, davidsarah
2010-08-01 12:23:15pitrousetmessageid: <>
2010-08-01 12:23:13pitroulinkissue7952 messages
2010-08-01 12:23:12pitroucreate