Clarify the example by explicitly importing the fcntl module -- this
avoid being fooled into thinking that fcntl and FCNTL are the same thing -- they aren't! (fcntl is the extension, FCNTL.py is h2py output that defines all the constants). (XXX The example is still weird -- I think there's a more portable way to do locking now. That's for someone else to fix...)
This commit is contained in:
parent
336a201d4f
commit
cf6905f986
|
@ -63,13 +63,13 @@ opcodes in the C include files \code{<sys/fcntl.h>} and
|
|||
Examples (all on a SVR4 compliant system):
|
||||
|
||||
\begin{verbatim}
|
||||
import struct, FCNTL
|
||||
import struct, fcntl, FCNTL
|
||||
|
||||
file = open(...)
|
||||
rv = fcntl(file.fileno(), FCNTL.O_NDELAY, 1)
|
||||
|
||||
lockdata = struct.pack('hhllhh', FCNTL.F_WRLCK, 0, 0, 0, 0, 0)
|
||||
rv = fcntl(file.fileno(), FCNTL.F_SETLKW, lockdata)
|
||||
rv = fcntl.fcntl(file.fileno(), FCNTL.F_SETLKW, lockdata)
|
||||
\end{verbatim}
|
||||
|
||||
Note that in the first example the return value variable \code{rv} will
|
||||
|
|
Loading…
Reference in New Issue