mirror of
https://github.com/python/cpython.git
synced 2025-08-04 00:48:58 +00:00
Oops, ".pythonrc.py" should *always* be marked with \file{}; one occurrance
escaped with \var{}.
This commit is contained in:
parent
5493205ba4
commit
9d2f7d414d
2 changed files with 2 additions and 2 deletions
|
@ -35,7 +35,7 @@ generally not a good idea.
|
|||
|
||||
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
|
||||
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
|
||||
level can look for a variable \code{user.spam_verbose}, as follows:
|
||||
|
||||
|
|
|
@ -35,7 +35,7 @@ generally not a good idea.
|
|||
|
||||
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
|
||||
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
|
||||
level can look for a variable \code{user.spam_verbose}, as follows:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue