Use source reST role instead of file where it makes sense.

source generates a nifty link to the Mercurial web viewer.
This commit is contained in:
Éric Araujo 2012-03-05 16:43:41 +01:00
parent 47546e6e3d
commit 76c6aa860c
2 changed files with 4 additions and 4 deletions

View File

@ -261,8 +261,8 @@ behave slightly differently from real Capsules. Specifically:
copy as you see fit.)
You can find :file:`capsulethunk.h` in the Python source distribution
in the :file:`Doc/includes` directory. We also include it here for
your reference; here is :file:`capsulethunk.h`:
as :source:`Doc/includes/capsulethunk.h`. We also include it here for
your convenience:
.. literalinclude:: ../includes/capsulethunk.h

View File

@ -365,7 +365,7 @@ and more.
You can learn about this by interactively experimenting with the :mod:`re`
module. If you have Tkinter available, you may also want to look at
:file:`Tools/scripts/redemo.py`, a demonstration program included with the
:source:`Tools/scripts/redemo.py`, a demonstration program included with the
Python distribution. It allows you to enter REs and strings, and displays
whether the RE matches or fails. :file:`redemo.py` can be quite useful when
trying to debug a complicated RE. Phil Schwartz's `Kodos
@ -501,7 +501,7 @@ more convenient. If a program contains a lot of regular expressions, or re-uses
the same ones in several locations, then it might be worthwhile to collect all
the definitions in one place, in a section of code that compiles all the REs
ahead of time. To take an example from the standard library, here's an extract
from :file:`xmllib.py`::
from the deprecated :mod:`xmllib` module::
ref = re.compile( ... )
entityref = re.compile( ... )