|
| 1 | +% Manual text and implementation by Jaap Vermeulen |
| 2 | +\section{Standard Module \sectcode{posixfile}} |
| 3 | +\bimodindex{posixfile} |
| 4 | +\indexii{posix}{file object} |
| 5 | + |
| 6 | +This module implements some additional functionality over the built-in |
| 7 | +file objects. In particular, it implements file locking, control over |
| 8 | +the file flags, and an easy interface to duplicate the file object. |
| 9 | +The module defines a new file object, the posixfile object. It |
| 10 | +inherits all the standard file object methods and adds the methods |
| 11 | +described below. |
| 12 | + |
| 13 | +To instantiate a posixfile object, use the \code{open()} function in |
| 14 | +the posixfile module. The resulting object looks and feels the same as |
| 15 | +a standard file object. |
| 16 | + |
| 17 | +The posixfile module defines the following constants: |
| 18 | + |
| 19 | +\renewcommand{\indexsubitem}{(in module posixfile)} |
| 20 | +\begin{datadesc}{SEEK_SET} |
| 21 | +offset is calculated from the start of the file |
| 22 | +\end{datadesc} |
| 23 | + |
| 24 | +\begin{datadesc}{SEEK_CUR} |
| 25 | +offset is calculated from the current position in the file |
| 26 | +\end{datadesc} |
| 27 | + |
| 28 | +\begin{datadesc}{SEEK_END} |
| 29 | +offset is calculated from the end of the file |
| 30 | +\end{datadesc} |
| 31 | + |
| 32 | +The posixfile module defines the following functions: |
| 33 | + |
| 34 | +\renewcommand{\indexsubitem}{(in module posixfile)} |
| 35 | +\begin{funcdesc}{open}{filename\, mode} |
| 36 | + Create a new posixfile object with the given filename and mode. The |
| 37 | + filename and mode are interpreted the same way as the \code{open()} |
| 38 | + builtin function. |
| 39 | +\end{funcdesc} |
| 40 | + |
| 41 | +\begin{funcdesc}{openfile}{fileobject} |
| 42 | + Create a new posixfile object with the given standard file object. |
| 43 | + The resulting object has the same filename and mode as the original |
| 44 | + file object. |
| 45 | +\end{funcdesc} |
| 46 | + |
| 47 | +The posixfile object defines the following additional methods: |
| 48 | + |
| 49 | +\renewcommand{\indexsubitem}{(posixfile method)} |
| 50 | +\begin{funcdesc}{lock}{fmt\, len\, start\, whence} |
| 51 | + Lock the specified section of the file that the file object is |
| 52 | + referring to. The arguments \code{\var{len}}, \code{\var{start}} |
| 53 | + and \code{\var{whence}} are optional with the understanding that |
| 54 | + if \code{\var{start}} is used \code{\var{len}} becomes mandatory, |
| 55 | + and if \code{\var{whence}} is used \code{\var{len}} and |
| 56 | + \code{\var{start}} become mandatory. The format is explained |
| 57 | + below in a table. The length argument specifies the length of the |
| 58 | + section that should be locked. The default is \code{0}. The start |
| 59 | + specifies the starting offset of the section. The default is |
| 60 | + \code{0}. The whence argument specifies where the offset is |
| 61 | + relative to. It accepts one of the constants \code{SEEK_SET}, |
| 62 | + \code{SEEK_CUR} or \code{SEEK_END}. The default is \code{SEEK_SET}. |
| 63 | + For more information about the arguments refer to the fcntl |
| 64 | + manual page on your system. |
| 65 | +\end{funcdesc} |
| 66 | + |
| 67 | +\begin{funcdesc}{flags}{fmt} |
| 68 | + Set the specified flags for the file that the file object is referring |
| 69 | + to. The new flags are ORed with the old flags, unless specified |
| 70 | + otherwise. The format is explained below in a table. Without |
| 71 | + arguments a string indicating the current flags is returned (this is |
| 72 | + the same as the '?'modifier). For more information about the flags |
| 73 | + refer to the fcntl manual page on your system. |
| 74 | +\end{funcdesc} |
| 75 | + |
| 76 | +\begin{funcdesc}{dup}{} |
| 77 | + Duplicate the file object and the underlying file pointer and file |
| 78 | + descriptor. The resulting object behaves as if it were newly |
| 79 | + opened. |
| 80 | +\end{funcdesc} |
| 81 | + |
| 82 | +\begin{funcdesc}{dup2}{fd} |
| 83 | + Duplicate the file object and the underlying file pointer and file |
| 84 | + descriptor. The new object will have the given file descriptor. |
| 85 | + Otherwise the resulting object behaves as if it were newly opened. |
| 86 | +\end{funcdesc} |
| 87 | + |
| 88 | +\begin{funcdesc}{file}{} |
| 89 | + Return the standard file object that the posixfile object is based |
| 90 | + on. This is sometimes necessary for functions that insist on a |
| 91 | + standard file object. |
| 92 | +\end{funcdesc} |
| 93 | + |
| 94 | +All methods return \code{IOError} when the request fails. |
| 95 | + |
| 96 | +Format characters for the \code{lock()} method have the following meaning: |
| 97 | + |
| 98 | +\begin{tableii}{|c|l|}{samp}{Format}{Meaning} |
| 99 | + \lineii{u}{unlock the specified region} |
| 100 | + \lineii{r}{request a read lock for the specified section} |
| 101 | + \lineii{w}{request a write lock for the specified section} |
| 102 | +\end{tableii} |
| 103 | + |
| 104 | +In addition the following modifiers can be added to the format: |
| 105 | + |
| 106 | +\begin{tableiii}{|c|l|c|}{samp}{Modifier}{Meaning}{Notes} |
| 107 | + \lineiii{|}{wait until the lock has been granted}{} |
| 108 | + \lineiii{?}{return the first lock conflicting with the requested lock, |
| 109 | + or \code{None} if there is no conflict.}{(1)} |
| 110 | +\end{tableiii} |
| 111 | + |
| 112 | +Note: |
| 113 | + |
| 114 | +(1) The lock returned is in the format \code{(mode, len, start, |
| 115 | +whence, pid)} where mode is a character representing the type of lock |
| 116 | +('r' or 'w'). This modifier prevents a request from being granted; it |
| 117 | +is for query purposes only. |
| 118 | + |
| 119 | +Format character for the \code{flags()} method have the following meaning: |
| 120 | + |
| 121 | +\begin{tableii}{|c|l|}{samp}{Format}{Meaning} |
| 122 | + \lineii{a}{append only flag} |
| 123 | + \lineii{c}{close on exec flag} |
| 124 | + \lineii{n}{no delay flag (also called non-blocking flag)} |
| 125 | + \lineii{s}{synchronization flag} |
| 126 | +\end{tableii} |
| 127 | + |
| 128 | +In addition the following modifiers can be added to the format: |
| 129 | + |
| 130 | +\begin{tableiii}{|c|l|c|}{samp}{Modifier}{Meaning}{Notes} |
| 131 | + \lineiii{!}{turn the specified flags 'off', instead of the default 'on'}{(1)} |
| 132 | + \lineiii{=}{replace the flags, instead of the default 'OR' operation}{(1)} |
| 133 | + \lineiii{?}{return a string in which the characters represent the flags that |
| 134 | + are set.}{(2)} |
| 135 | +\end{tableiii} |
| 136 | + |
| 137 | +Note: |
| 138 | + |
| 139 | +(1) The \code{!} and \code{=} modifiers are mutually exclusive. |
| 140 | + |
| 141 | +(2) This string represents the flag after they may have been altered |
| 142 | +by the same call. |
| 143 | + |
| 144 | +Examples: |
| 145 | + |
| 146 | +\bcode\begin{verbatim} |
| 147 | +from posixfile import * |
| 148 | +
|
| 149 | +file = open('/tmp/test', 'w') |
| 150 | +file.lock('w|') |
| 151 | +... |
| 152 | +file.lock('u') |
| 153 | +file.close() |
| 154 | +\end{verbatim}\ecode |
0 commit comments