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 vstinner
Recipients jcea, pitrou, vstinner
Date 2011-06-20.16:01:05
SpamBayes Score 3.6743526e-07
Marked as misclassified No
Message-id <1308585666.14.0.600401665588.issue12213@psf.upfronthosting.co.za>
In-reply-to
Content
>> My patch tries to fix interlaced read-write by always calling flush(),
>
> Why do you need to call flush()? Can't you read from the buffer?

Hum, my patch does not always call flush of the reader and the writer. On read, it flushs the writer. On write, it "flushes" the reader (undo readahead).

It is maybe possible to do better (do something faster), but there should be some tricky cases with seek().
History
Date User Action Args
2011-06-20 16:01:06vstinnersetrecipients: + vstinner, jcea, pitrou
2011-06-20 16:01:06vstinnersetmessageid: <1308585666.14.0.600401665588.issue12213@psf.upfronthosting.co.za>
2011-06-20 16:01:05vstinnerlinkissue12213 messages
2011-06-20 16:01:05vstinnercreate