Commit 9d2f7d41 authored by Fred Drake's avatar Fred Drake

Oops, ".pythonrc.py" should *always* be marked with \file{}; one occurrance

escaped with \var{}.
parent 5493205b
...@@ -35,7 +35,7 @@ generally not a good idea. ...@@ -35,7 +35,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 \var{.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 \code{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:
......
...@@ -35,7 +35,7 @@ generally not a good idea. ...@@ -35,7 +35,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 \var{.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 \code{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:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment