classification
Title: fcntl footnote about O_SHLOCK and O_EXLOCK is misleading
Type: behavior Stage: needs patch
Components: Documentation Versions: Python 3.0, Python 3.1, Python 2.7, Python 2.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: georg.brandl, r.david.murray
Priority: low Keywords: easy

Created on 2009-06-04 21:38 by r.david.murray, last changed 2009-06-08 13:35 by georg.brandl. This issue is now closed.

Messages (2)
msg88904 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-06-04 21:38
At the bottom of http://docs.python.org/library/fcntl.html there is a
"see also" section for the os module that says:

    If the locking flags O_SHLOCK and O_EXLOCK are present in the os
module, the os.open() function provides a more platform-independent
alternative to the lockf() and flock() functions.

However, those flags are documented as being "unix only" (ie: no
windows), and in fact Linux does not support them.  Alan Cox rejected
support for them back in 2000 according to this linux kernel posting:

  http://lkml.indiana.edu/hypermail/linux/kernel/0005.1/1309.html

so it doesn't seem likely linux will ever support them.

Thus, to say that they provide a "more platform independent-alternative"
would appear to be false, since they appear to only be supported on BSD
and derivitives.
msg89079 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-06-08 13:35
Thanks, fixed in r73294.
History
Date User Action Args
2009-06-08 13:35:02georg.brandlsetstatus: open -> closed
resolution: fixed
messages: + msg89079
2009-06-04 21:38:31r.david.murraycreate