RetroSearch Browse

Thu Mar 12 22:16:34 CET 2009 · https://mail.python.org/pipermail/python-dev/2009-March/087138.html

Jim Jewett wrote:
> On 3/12/09, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>> It is starting to look as though flush (and close?) should take an
>>> optional wait parameter, to indicate how much re-assurance you're
>>> willing to wait for.
> 
>> Unfortunately, such a thing would be unimplementable on most of today's
>> operating systems.
> 
> What am I missing?

As somebody else remarked: I mistook your proposal for a "wait"
parameter to denote a time that you want to wait for the data to appear
on disk, specified, e.g., in seconds.

It didn't occur to me that it might be a unit-less unscaled value, which
I find an ugly API.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-March/087138.html below:

[Python-Dev] wait time [was: Ext4 data loss]