[Python-Dev] Does Python need a file locking module (slightly higher level)?
Jon Ribbens
jon+python-dev at unequivocal.co.uk
Tue Oct 23 02:08:03 CEST 2007
On Tue, Oct 23, 2007 at 12:16:41PM +1300, Greg Ewing wrote:
> skip at pobox.com wrote:
> > This interface follows the completely stupid semantics of System V and
> > IEEE Std 1003.1-1988 (``POSIX.1'') that require that all locks
> > associated with a file for a given process are removed when any file
> > descriptor for that file is closed by that process.... Flock(2) is
> > recommended for applications that want to ensure the integrity of their
> > locks when using library routines or wish to pass locks to their
> > children.
> >
> > I guess the BSD folks were a bit upset when they wrote that.
>
> That sounds more like something written by the GNU folks than
> the BSD folks.
It's from BSD. The earliest I can find it is 4.4BSD. It's still in the
latest versions of OpenBSD, NetBSD and FreeBSD.
More information about the Python-Dev
mailing list