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/087076.html below:

[Python-Dev] Ext4 data loss

[Python-Dev] Ext4 data lossLie Ryan lie.1296 at gmail.com
Wed Mar 11 17:20:30 CET 2009
Scott Dial wrote:
> Aahz wrote:
>> On Wed, Mar 11, 2009, Antoine Pitrou wrote:
>>> After Hrvoje's message, let me rephrase my suggestion. Let's instead allow:
>>>    open(..., sync_on="close")
>>>    open(..., sync_on="flush")
>>>
>>> with a default of None meaning no implicit syncs.
>> That looks good, though I'd prefer using named constants rather than
>> strings.
> 
> I would agree, but where do you put them? Since open is a built-in,
> where would you suggest placing such constants (assuming we don't want
> to pollute the built-in namespace)?
> 

I actually prefer strings. Just like 'w' or 'r' in open().

Or why not add "f" "c" as modes?

open('file.txt', 'wf')

open for writing, sync on flush

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