As a policy, Python doesn't run user-specified code on startup of
Python programs. (Only interactive sessions execute the script
-specified in the \code{PYTHONSTARTUP} environment variable if it exists).
+specified in the \envvar{PYTHONSTARTUP} environment variable if it
+exists).
However, some programs or sites may find it convenient to allow users
to have a standard customization file, which gets run when a program
module \module{user}'s) global namespace. Errors during this phase
are not caught; that's up to the program that imports the
\module{user} module, if it wishes. The home directory is assumed to
-be named by the \code{HOME} environment variable; if this is not set,
+be named by the \envvar{HOME} environment variable; if this is not set,
the current directory is used.
The user's \file{.pythonrc.py} could conceivably test for
As a policy, Python doesn't run user-specified code on startup of
Python programs. (Only interactive sessions execute the script
-specified in the \code{PYTHONSTARTUP} environment variable if it exists).
+specified in the \envvar{PYTHONSTARTUP} environment variable if it
+exists).
However, some programs or sites may find it convenient to allow users
to have a standard customization file, which gets run when a program
module \module{user}'s) global namespace. Errors during this phase
are not caught; that's up to the program that imports the
\module{user} module, if it wishes. The home directory is assumed to
-be named by the \code{HOME} environment variable; if this is not set,
+be named by the \envvar{HOME} environment variable; if this is not set,
the current directory is used.
The user's \file{.pythonrc.py} could conceivably test for