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

Showing content from https://mail.python.org/pipermail/python-dev/2007-October/074995.html below:

[Python-Dev] Does Python need a file locking module (slightly higher level)?

• Previous message: [Python-Dev] Does Python need a file locking module (slightly higher level)?
• Next message: [Python-Dev] Does Python need a file locking module (slightly higher level)?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.

--
Greg

• Previous message: [Python-Dev] Does Python need a file locking module (slightly higher level)?
• Next message: [Python-Dev] Does Python need a file locking module (slightly higher level)?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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