You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/birkenfeld'closed_at=<Date2009-06-08.13:35:02.473>created_at=<Date2009-06-04.21:38:31.803>labels= ['easy', 'type-bug', 'docs']
title='fcntl footnote about O_SHLOCK and O_EXLOCK is misleading'updated_at=<Date2009-06-08.13:35:02.471>user='https://github.com/bitdancer'
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:
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.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: