Amir Michail schrieb: > Paolo Pantaleo wrote: >> 27 Aug 2006 00:44:33 -0700, Amir Michail <[EMAIL PROTECTED]>: >>> Hi, >>> >>> Trying to open a file for writing that is already open for writing >>> should result in an exception. >>> >>> It's all too easy to accidentally open a shelve for writing twice and >>> this can lead to hard to track down database corruption errors. >>> >>> Amir >>> >>> -- >>> http://mail.python.org/mailman/listinfo/python-list >>> >> Even if it could be strange, the OS usually allow you to open a file >> twice, that's up to the programmer to ensure the consistency of the >> operations. >> >> PAolo >> > > But if this is usually a serious bug, shouldn't an exception be raised?
executing "rm -rf /" via subprocess is usually also a bad idea. So? No language can prevent you from doing such mistake. And there is no way to know if a file is opened twice - it might that you open the same file twice via e.g. a network share. No way to know that it is the same file. Diez -- http://mail.python.org/mailman/listinfo/python-list
