RetroSearch Browse

Wed Mar 11 17:04:41 CET 2009 · https://mail.python.org/pipermail/python-dev/2009-March/087073.html

On Wed, Mar 11, 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)?

The os module, of course, like the existing O_* constants.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

"All problems in computer science can be solved by another level of     
indirection."  --Butler Lampson

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

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

[Python-Dev] Ext4 data loss