[Python-checkins] devguide: Use PEP role for PEP link.

chris.jerdonek python-checkins at python.org
Thu Nov 29 04:00:49 CET 2012


http://hg.python.org/devguide/rev/a0bfb97184e3
changeset:   576:a0bfb97184e3
user:        Chris Jerdonek <chris.jerdonek at gmail.com>
date:        Wed Nov 28 18:36:49 2012 -0800
summary:
  Use PEP role for PEP link.

files:
  langchanges.rst |  4 +---
  1 files changed, 1 insertions(+), 3 deletions(-)


diff --git a/langchanges.rst b/langchanges.rst
--- a/langchanges.rst
+++ b/langchanges.rst
@@ -41,7 +41,7 @@
 Once you are certain you have a language change proposal which will appeal to
 the general Python community, you can begin the process of officially proposing
 the change. This process is the Python Enhancement Proposal (PEP) process.
-`PEP 1`_ describes it in detail.
+:PEP:`1` describes it in detail.
 
 You will first need a PEP that you will present to python-ideas. You may be a
 little hazy on the technical details as various core developers can help with
@@ -61,5 +61,3 @@
 language change will be introduced in the next release of Python. Otherwise
 your PEP will be recorded as rejected along with an explanation as to why so
 that others do not propose the same language change in the future.
-
-.. _PEP 1: http://www.python.org/dev/peps/pep-0001/

-- 
Repository URL: http://hg.python.org/devguide


More information about the Python-checkins mailing list