A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Ext4 data loss

[Python-Dev] Ext4 data loss [Python-Dev] Ext4 data lossHrvoje Niksic hrvoje.niksic at avl.com
Wed Mar 11 15:14:49 CET 2009
Christian Heimes wrote:
> Guido van Rossum wrote:
>> Let's not think too Unix-specific. If we add such an API it should do
>> something on Windows too -- the app shouldn't have to test for the
>> presence of the API. (And thus the API probably shouldn't be called
>> fsync.)
> 
> In my initial proposal one and a half hour earlier I suggested 'sync()'
> as the name of the method and 'synced' as the name of the flag that
> forces a fsync() call during the close operation.

Maybe it would make more sense for "synced" to force fsync() on each 
flush, not only on close.  I'm not sure how useful it is, but that's 
what "synced" would imply to me.  Maybe it would be best to avoid having 
such a variable, and expose a close_sync() method instead?
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4