summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorÉric Araujo <merwok@netwok.org>2012-03-05 14:50:37 (GMT)
committerÉric Araujo <merwok@netwok.org>2012-03-05 14:50:37 (GMT)
commitfdfaf0aba2fe8cc8e985d64bdd929b16a1c37690 (patch)
treeb1cf9e1c8057056c866ad6a3cd28c6981585f956
parentd3899e320fa4c10166c5eb7dc7996d15dd541f46 (diff)
downloadcpython-fdfaf0aba2fe8cc8e985d64bdd929b16a1c37690.zip
cpython-fdfaf0aba2fe8cc8e985d64bdd929b16a1c37690.tar.gz
cpython-fdfaf0aba2fe8cc8e985d64bdd929b16a1c37690.tar.bz2
Use source reST role instead of file where it makes sense.
source generates a nifty link to the Mercurial web viewer.
-rw-r--r--Doc/howto/cporting.rst4
-rw-r--r--Doc/howto/regex.rst4
2 files changed, 4 insertions, 4 deletions
diff --git a/Doc/howto/cporting.rst b/Doc/howto/cporting.rst
index 98db9dd..bea2153 100644
--- a/Doc/howto/cporting.rst
+++ b/Doc/howto/cporting.rst
@@ -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
diff --git a/Doc/howto/regex.rst b/Doc/howto/regex.rst
index 07a8b56..3ac03ca 100644
--- a/Doc/howto/regex.rst
+++ b/Doc/howto/regex.rst
@@ -360,7 +360,7 @@ and more.
You can learn about this by interactively experimenting with the :mod:`re`
module. If you have :mod:`tkinter` available, you may also want to look at
-:file:`Tools/demo/redemo.py`, a demonstration program included with the
+:source:`Tools/demo/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
@@ -495,7 +495,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 the now deprecated :file:`xmllib.py`::
+from the now-defunct Python 2 standard :mod:`xmllib` module::
ref = re.compile( ... )
entityref = re.compile( ... )