Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Logical markup.

This commit is contained in:
Fred Drake 1998-03-08 07:14:20 +00:00
parent b991f8d2e0
commit 8fab8cf211
2 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Doc/lib/libuser.tex
View File

@ -17,13 +17,14 @@ that wishes to use the mechanism must execute the statement
import user import user
\end{verbatim} \end{verbatim}
The \code{user} module looks for a file \file{.pythonrc.py} in the user's The \module{user} module looks for a file \file{.pythonrc.py} in the user's
home directory and if it can be opened, exececutes it (using home directory and if it can be opened, exececutes it (using
\code{execfile()}) in its own (i.e. the module \code{user}'s) global \function{execfile()}\bifuncindex{execfile}) in its own (i.e. the
namespace. Errors during this phase are not caught; that's up to the module \module{user}'s) global namespace. Errors during this phase
program that imports the \code{user} module, if it wishes. The home are not caught; that's up to the program that imports the
directory is assumed to be named by the \code{HOME} environment \module{user} module, if it wishes. The home directory is assumed to
variable; if this is not set, the current directory is used. be named by the \code{HOME} environment variable; if this is not set,
the current directory is used.
The user's \file{.pythonrc.py} could conceivably test for The user's \file{.pythonrc.py} could conceivably test for
\code{sys.version} if it wishes to do different things depending on \code{sys.version} if it wishes to do different things depending on
@ -37,7 +38,7 @@ generally not a good idea.
A suggestion for programmers who wish to use this mechanism: a simple A suggestion for programmers who wish to use this mechanism: a simple
way to let users specify options for your package is to have them way to let users specify options for your package is to have them
define variables in their \file{.pythonrc.py} file that you test in define variables in their \file{.pythonrc.py} file that you test in
your module. For example, a module \code{spam} that has a verbosity your module. For example, a module \module{spam} that has a verbosity
level can look for a variable \code{user.spam_verbose}, as follows: level can look for a variable \code{user.spam_verbose}, as follows:
\begin{verbatim} \begin{verbatim}

15
Doc/libuser.tex
View File

@ -17,13 +17,14 @@ that wishes to use the mechanism must execute the statement
import user import user
\end{verbatim} \end{verbatim}
The \code{user} module looks for a file \file{.pythonrc.py} in the user's The \module{user} module looks for a file \file{.pythonrc.py} in the user's
home directory and if it can be opened, exececutes it (using home directory and if it can be opened, exececutes it (using
\code{execfile()}) in its own (i.e. the module \code{user}'s) global \function{execfile()}\bifuncindex{execfile}) in its own (i.e. the
namespace. Errors during this phase are not caught; that's up to the module \module{user}'s) global namespace. Errors during this phase
program that imports the \code{user} module, if it wishes. The home are not caught; that's up to the program that imports the
directory is assumed to be named by the \code{HOME} environment \module{user} module, if it wishes. The home directory is assumed to
variable; if this is not set, the current directory is used. be named by the \code{HOME} environment variable; if this is not set,
the current directory is used.
The user's \file{.pythonrc.py} could conceivably test for The user's \file{.pythonrc.py} could conceivably test for
\code{sys.version} if it wishes to do different things depending on \code{sys.version} if it wishes to do different things depending on
@ -37,7 +38,7 @@ generally not a good idea.
A suggestion for programmers who wish to use this mechanism: a simple A suggestion for programmers who wish to use this mechanism: a simple
way to let users specify options for your package is to have them way to let users specify options for your package is to have them
define variables in their \file{.pythonrc.py} file that you test in define variables in their \file{.pythonrc.py} file that you test in
your module. For example, a module \code{spam} that has a verbosity your module. For example, a module \module{spam} that has a verbosity
level can look for a variable \code{user.spam_verbose}, as follows: level can look for a variable \code{user.spam_verbose}, as follows:
\begin{verbatim} \begin{verbatim}