diff options
author | Fred Drake <fdrake@acm.org> | 1998-02-09 20:27:12 (GMT) |
---|---|---|
committer | Fred Drake <fdrake@acm.org> | 1998-02-09 20:27:12 (GMT) |
commit | 65b32f7f7448ae9a5f8cf3500ee7e127aa740b77 (patch) | |
tree | cd0dd6be021dc851faca8f2f7a9a33420c2c3834 /Doc/lib/libos.tex | |
parent | 41785fb8644b66f4f17e292e9f96e870ae8b2764 (diff) | |
download | cpython-65b32f7f7448ae9a5f8cf3500ee7e127aa740b77.zip cpython-65b32f7f7448ae9a5f8cf3500ee7e127aa740b77.tar.gz cpython-65b32f7f7448ae9a5f8cf3500ee7e127aa740b77.tar.bz2 |
Consistently use \POSIX{} to denote POSIX. There were at least two different
ways to do it previously (not counting module names).
Diffstat (limited to 'Doc/lib/libos.tex')
-rw-r--r-- | Doc/lib/libos.tex | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Doc/lib/libos.tex b/Doc/lib/libos.tex index 1853b3f..763d2f3 100644 --- a/Doc/lib/libos.tex +++ b/Doc/lib/libos.tex @@ -13,7 +13,7 @@ exports the same functions and data as found there. The design of all 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! @@ -43,20 +43,20 @@ more portable than \code{posixpath.split(\var{file})}. \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} @@ -67,7 +67,7 @@ or \code{None} if only one separator character exists. This is set to \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} |