ways to do it previously (not counting module names).
\end{funcdesc}
\begin{funcdesc}{tod_gettime}{}
-Returns the time (in seconds since the Epoch, in UCT, as for POSIX) from
+Returns the time (in seconds since the Epoch, in UCT, as for \POSIX{}) from
a time server.
\end{funcdesc}
\label{module-locale}
-The \code{locale} module opens access to the POSIX locale database and
-functionality. The POSIX locale mechanism allows applications to
-integrate certain cultural aspects into an applications, without
+The \code{locale} module opens access to the \POSIX{} locale database
+and functionality. The \POSIX{} locale mechanism allows applications
+to integrate certain cultural aspects into an applications, without
requiring the programmer to know all the specifics of each country
where the software is executed.
3798 Re: a few questions about the Mac implementation
3799 Re: PROPOSAL: A Generic Python Object Interface for Python C Modules
3802 Re: executable python scripts
-3803 Re: POSIX wait and SIGCHLD
+3803 Re: \POSIX{} wait and SIGCHLD
>>> s.quit()
'205 news.cwi.nl closing connection. Goodbye.'
>>>
Python's built-in OS dependent modules is such that as long as the same
functionality is available, it uses the same interface; e.g., the
function \code{os.stat(\var{file})} returns stat info about a \var{file} in a
-format compatible with the POSIX interface.
+format compatible with the \POSIX{} interface.
Extensions peculiar to a particular OS are also available through the
\code{os} module, but using them is of course a threat to portability!
\begin{datadesc}{curdir}
The constant string used by the OS to refer to the current directory,
-e.g. \code{'.'} for POSIX or \code{':'} for the Mac.
+e.g. \code{'.'} for \POSIX{} or \code{':'} for the Mac.
\end{datadesc}
\begin{datadesc}{pardir}
The constant string used by the OS to refer to the parent directory,
-e.g. \code{'..'} for POSIX or \code{'::'} for the Mac.
+e.g. \code{'..'} for \POSIX{} or \code{'::'} for the Mac.
\end{datadesc}
\begin{datadesc}{sep}
The character used by the OS to separate pathname components,
-e.g. \code{'/'} for POSIX or \code{':'} for the Mac. Note that knowing this
-is not sufficient to be able to parse or concatenate pathnames---better
-use \code{os.path.split()} and \code{os.path.join()}---but it is
-occasionally useful.
+e.g. \code{'/'} for \POSIX{} or \code{':'} for the Mac. Note that
+knowing this is not sufficient to be able to parse or concatenate
+pathnames --- better use \code{os.path.split()} and
+\code{os.path.join()}---but it is occasionally useful.
\end{datadesc}
\begin{datadesc}{altsep}
\begin{datadesc}{pathsep}
The character conventionally used by the OS to separate search patch
-components (as in \code{\$PATH}), e.g.\ \code{':'} for POSIX or
+components (as in \code{\$PATH}), e.g.\ \code{':'} for \POSIX{} or
\code{';'} for MS-DOS.
\end{datadesc}
\bimodindex{posix}
This module provides access to operating system functionality that is
-standardized by the C Standard and the POSIX standard (a thinly disguised
+standardized by the C Standard and the \POSIX{} standard (a thinly disguised
\UNIX{} interface).
\strong{Do not import this module directly.} Instead, import the
\refstmodindex{os}
The descriptions below are very terse; refer to the corresponding
-\UNIX{} manual (or POSIX documentation) entry for more information.
+\UNIX{} manual (or \POSIX{} documentation) entry for more information.
Arguments called \var{path} refer to a pathname given as a string.
Errors are reported as exceptions; the usual exceptions are given
\renewcommand{\indexsubitem}{(exception in module posix)}
\begin{excdesc}{error}
-This exception is raised when a POSIX function returns a
-POSIX-related error (e.g., not for illegal argument types). Its
+This exception is raised when a \POSIX{} function returns a
+\POSIX{}-related error (e.g., not for illegal argument types). Its
string value is \code{'posix.error'}. The accompanying value is a
pair containing the numeric error code from \code{errno} and the
corresponding string, as would be printed by the C function
\end{funcdesc}
\begin{funcdesc}{mkfifo}{path\optional{\, mode}}
-Create a FIFO (a POSIX named pipe) named \var{path} with numeric mode
+Create a FIFO (a \POSIX{} named pipe) named \var{path} with numeric mode
\var{mode}. The default \var{mode} is 0666 (octal). The current
umask value is first masked out from the mode.
(Not on MS-DOS.)
\label{module-posixpath}
\stmodindex{posixpath}
-This module implements some useful functions on POSIX pathnames.
+This module implements some useful functions on \POSIX{} pathnames.
\strong{Do not import this module directly.} Instead, import the
module \code{os} and use \code{os.path}.
function checks whether \var{p}'s parent, \file{\var{p}/..}, is on a
different device than \var{p}, or whether \file{\var{p}/..} and
\var{p} point to the same i-node on the same device --- this should
-detect mount points for all \UNIX{} and POSIX variants.
+detect mount points for all \UNIX{} and \POSIX{} variants.
\end{funcdesc}
\begin{funcdesc}{join}{p\optional{\, q\optional{\, ...}}}
\section{Built-in Module \sectcode{termios}}
\label{module-termios}
\bimodindex{termios}
-\indexii{Posix}{I/O control}
+\indexii{\POSIX{}}{I/O control}
\indexii{tty}{I/O control}
\renewcommand{\indexsubitem}{(in module termios)}
-This module provides an interface to the Posix calls for tty I/O
-control. For a complete description of these calls, see the Posix or
+This module provides an interface to the \POSIX{} calls for tty I/O
+control. For a complete description of these calls, see the \POSIX{} or
\UNIX{} manual pages. It is only available for those \UNIX{} versions
-that support Posix \code{termios} style tty I/O control (and then
+that support \POSIX{} \code{termios} style tty I/O control (and then
only if configured at installation time).
All functions in this module take a file descriptor \var{fd} as their
%
\section{Standard Module \sectcode{TERMIOS}}
\stmodindex{TERMIOS}
-\indexii{Posix}{I/O control}
+\indexii{\POSIX{}}{I/O control}
\indexii{tty}{I/O control}
\renewcommand{\indexsubitem}{(in module TERMIOS)}
This module defines the symbolic constants required to use the
-\code{termios} module (see the previous section). See the Posix or
+\code{termios} module (see the previous section). See the \POSIX{} or
\UNIX{} manual pages (or the source) for a list of those constants.
\refbimodindex{termios}
\index{semaphores, binary}
The module is optional. It is supported on Windows NT and '95, SGI
-IRIX, Solaris 2.x, as well as on systems that have a POSIX thread
+IRIX, Solaris 2.x, as well as on systems that have a \POSIX{} thread
(a.k.a. ``pthread'') implementation.
\index{pthreads}
\indexii{threads}{posix}
\begin{description}
\item[posix]
---- The most common Posix system calls (normally used via module \code{os}).
+--- The most common \POSIX{} system calls (normally used via module \code{os}).
\item[posixpath]
---- Common Posix pathname manipulations (normally used via \code{os.path}).
+--- Common \POSIX{} pathname manipulations (normally used via \code{os.path}).
\item[pwd]
--- The password database (\code{getpwnam()} and friends).
--- GNU's reinterpretation of dbm.
\item[termios]
---- Posix style tty control.
+--- \POSIX{} style tty control.
\item[TERMIOS]
--- The symbolic constants required to use the \code{termios} module.
\end{funcdesc}
\begin{funcdesc}{tod_gettime}{}
-Returns the time (in seconds since the Epoch, in UCT, as for POSIX) from
+Returns the time (in seconds since the Epoch, in UCT, as for \POSIX{}) from
a time server.
\end{funcdesc}
\label{module-locale}
-The \code{locale} module opens access to the POSIX locale database and
-functionality. The POSIX locale mechanism allows applications to
-integrate certain cultural aspects into an applications, without
+The \code{locale} module opens access to the \POSIX{} locale database
+and functionality. The \POSIX{} locale mechanism allows applications
+to integrate certain cultural aspects into an applications, without
requiring the programmer to know all the specifics of each country
where the software is executed.
3798 Re: a few questions about the Mac implementation
3799 Re: PROPOSAL: A Generic Python Object Interface for Python C Modules
3802 Re: executable python scripts
-3803 Re: POSIX wait and SIGCHLD
+3803 Re: \POSIX{} wait and SIGCHLD
>>> s.quit()
'205 news.cwi.nl closing connection. Goodbye.'
>>>
Python's built-in OS dependent modules is such that as long as the same
functionality is available, it uses the same interface; e.g., the
function \code{os.stat(\var{file})} returns stat info about a \var{file} in a
-format compatible with the POSIX interface.
+format compatible with the \POSIX{} interface.
Extensions peculiar to a particular OS are also available through the
\code{os} module, but using them is of course a threat to portability!
\begin{datadesc}{curdir}
The constant string used by the OS to refer to the current directory,
-e.g. \code{'.'} for POSIX or \code{':'} for the Mac.
+e.g. \code{'.'} for \POSIX{} or \code{':'} for the Mac.
\end{datadesc}
\begin{datadesc}{pardir}
The constant string used by the OS to refer to the parent directory,
-e.g. \code{'..'} for POSIX or \code{'::'} for the Mac.
+e.g. \code{'..'} for \POSIX{} or \code{'::'} for the Mac.
\end{datadesc}
\begin{datadesc}{sep}
The character used by the OS to separate pathname components,
-e.g. \code{'/'} for POSIX or \code{':'} for the Mac. Note that knowing this
-is not sufficient to be able to parse or concatenate pathnames---better
-use \code{os.path.split()} and \code{os.path.join()}---but it is
-occasionally useful.
+e.g. \code{'/'} for \POSIX{} or \code{':'} for the Mac. Note that
+knowing this is not sufficient to be able to parse or concatenate
+pathnames --- better use \code{os.path.split()} and
+\code{os.path.join()}---but it is occasionally useful.
\end{datadesc}
\begin{datadesc}{altsep}
\begin{datadesc}{pathsep}
The character conventionally used by the OS to separate search patch
-components (as in \code{\$PATH}), e.g.\ \code{':'} for POSIX or
+components (as in \code{\$PATH}), e.g.\ \code{':'} for \POSIX{} or
\code{';'} for MS-DOS.
\end{datadesc}
\bimodindex{posix}
This module provides access to operating system functionality that is
-standardized by the C Standard and the POSIX standard (a thinly disguised
+standardized by the C Standard and the \POSIX{} standard (a thinly disguised
\UNIX{} interface).
\strong{Do not import this module directly.} Instead, import the
\refstmodindex{os}
The descriptions below are very terse; refer to the corresponding
-\UNIX{} manual (or POSIX documentation) entry for more information.
+\UNIX{} manual (or \POSIX{} documentation) entry for more information.
Arguments called \var{path} refer to a pathname given as a string.
Errors are reported as exceptions; the usual exceptions are given
\renewcommand{\indexsubitem}{(exception in module posix)}
\begin{excdesc}{error}
-This exception is raised when a POSIX function returns a
-POSIX-related error (e.g., not for illegal argument types). Its
+This exception is raised when a \POSIX{} function returns a
+\POSIX{}-related error (e.g., not for illegal argument types). Its
string value is \code{'posix.error'}. The accompanying value is a
pair containing the numeric error code from \code{errno} and the
corresponding string, as would be printed by the C function
\end{funcdesc}
\begin{funcdesc}{mkfifo}{path\optional{\, mode}}
-Create a FIFO (a POSIX named pipe) named \var{path} with numeric mode
+Create a FIFO (a \POSIX{} named pipe) named \var{path} with numeric mode
\var{mode}. The default \var{mode} is 0666 (octal). The current
umask value is first masked out from the mode.
(Not on MS-DOS.)
\label{module-posixpath}
\stmodindex{posixpath}
-This module implements some useful functions on POSIX pathnames.
+This module implements some useful functions on \POSIX{} pathnames.
\strong{Do not import this module directly.} Instead, import the
module \code{os} and use \code{os.path}.
function checks whether \var{p}'s parent, \file{\var{p}/..}, is on a
different device than \var{p}, or whether \file{\var{p}/..} and
\var{p} point to the same i-node on the same device --- this should
-detect mount points for all \UNIX{} and POSIX variants.
+detect mount points for all \UNIX{} and \POSIX{} variants.
\end{funcdesc}
\begin{funcdesc}{join}{p\optional{\, q\optional{\, ...}}}
\section{Built-in Module \sectcode{termios}}
\label{module-termios}
\bimodindex{termios}
-\indexii{Posix}{I/O control}
+\indexii{\POSIX{}}{I/O control}
\indexii{tty}{I/O control}
\renewcommand{\indexsubitem}{(in module termios)}
-This module provides an interface to the Posix calls for tty I/O
-control. For a complete description of these calls, see the Posix or
+This module provides an interface to the \POSIX{} calls for tty I/O
+control. For a complete description of these calls, see the \POSIX{} or
\UNIX{} manual pages. It is only available for those \UNIX{} versions
-that support Posix \code{termios} style tty I/O control (and then
+that support \POSIX{} \code{termios} style tty I/O control (and then
only if configured at installation time).
All functions in this module take a file descriptor \var{fd} as their
%
\section{Standard Module \sectcode{TERMIOS}}
\stmodindex{TERMIOS}
-\indexii{Posix}{I/O control}
+\indexii{\POSIX{}}{I/O control}
\indexii{tty}{I/O control}
\renewcommand{\indexsubitem}{(in module TERMIOS)}
This module defines the symbolic constants required to use the
-\code{termios} module (see the previous section). See the Posix or
+\code{termios} module (see the previous section). See the \POSIX{} or
\UNIX{} manual pages (or the source) for a list of those constants.
\refbimodindex{termios}
\index{semaphores, binary}
The module is optional. It is supported on Windows NT and '95, SGI
-IRIX, Solaris 2.x, as well as on systems that have a POSIX thread
+IRIX, Solaris 2.x, as well as on systems that have a \POSIX{} thread
(a.k.a. ``pthread'') implementation.
\index{pthreads}
\indexii{threads}{posix}
\begin{description}
\item[posix]
---- The most common Posix system calls (normally used via module \code{os}).
+--- The most common \POSIX{} system calls (normally used via module \code{os}).
\item[posixpath]
---- Common Posix pathname manipulations (normally used via \code{os.path}).
+--- Common \POSIX{} pathname manipulations (normally used via \code{os.path}).
\item[pwd]
--- The password database (\code{getpwnam()} and friends).
--- GNU's reinterpretation of dbm.
\item[termios]
---- Posix style tty control.
+--- \POSIX{} style tty control.
\item[TERMIOS]
--- The symbolic constants required to use the \code{termios} module.
projects / python / commitdiff