Fix broken links in pep-0001.txt. Update the information with pointers to hg

and devguide.

pep-0001.txt

@@ -116,7 +116,7 @@ Dictator for Life, Guido van Rossum) can be consulted during the
 approval phase, and is the final arbiter of the draft's PEP-ability.
 
 As updates are necessary, the PEP author can check in new versions if
-they have SVN commit permissions, or can email new PEP versions to
+they have hg push privileges, or can email new PEP versions to
 the PEP editor for committing.
 
 Standards Track PEPs consist of two parts, a design document and a
@@ -129,11 +129,10 @@ or a URL to same -- before it can be considered Final.
 PEP authors are responsible for collecting community feedback on a PEP
 before submitting it for review. However, wherever possible, long
 open-ended discussions on public mailing lists should be avoided.
-Strategies to keep the
-discussions efficient include: setting up a separate SIG mailing list
-for the topic, having the PEP author accept private comments in the
-early design phases, setting up a wiki page, etc.  PEP authors should
-use their discretion here.
+Strategies to keep the discussions efficient include: setting up a 
+separate SIG mailing list for the topic, having the PEP author accept
+private comments in the early design phases, setting up a wiki page, etc.
+PEP authors should use their discretion here.
 
 Once the authors have completed a PEP, they must inform the PEP editor
 that it is ready for review.  PEPs are reviewed by the BDFL and his
@@ -266,8 +265,8 @@ optional and are described below.  All other headers are required. ::
 
     PEP: <pep number>
     Title: <pep title>
-    Version: <svn version string>
-    Last-Modified: <svn date string>
+    Version: <version string>
+    Last-Modified: <date string>
     Author: <list of authors' real names and optionally, email addrs>
   * Discussions-To: <email address>
     Status: <Draft | Active | Accepted | Deferred | Rejected |
@@ -366,7 +365,7 @@ When in doubt about where to send your changes, please check first
 with the PEP author and/or PEP editor.
 
 PEP authors who are also Python committers can update the
-PEPs themselves by using "svn commit" to commit their changes.
+PEPs themselves by using "hg push" to submit their changes.
 
 
 Transferring PEP Ownership
@@ -420,20 +419,13 @@ Once the PEP is ready for the repository, the PEP editor will:
 * List the PEP in PEP 0 (in two places: the categorized list, and the
   numeric list).
 
-* Add the PEP to SVN.  For Subversion repository instructions, see
-  `the FAQ for Developers
-  <http://www.python.org/dev/faq/#how-do-i-get-a-checkout-of-the-repository-read-only-and-read-write>`_.
+* Add the PEP to Mercurial.  For mercurial work flow instructions, follow
+  `The Python Developers Guide <http://docs.python.org/devguide>`_
 
-  The command to check out a read-only copy of the repository is::
+  The mercurial repo for the peps is::
 
-      svn checkout http://svn.python.org/projects/peps/trunk peps
+    http://hg.python.org/peps/
 
-  The command to check out a read-write copy of the repository is::
-
-      svn checkout svn+ssh://pythondev@svn.python.org/peps/trunk peps
-
-  In particular, the ``svn:eol-style`` property should be set to ``native``
-  and the ``svn:keywords`` property to ``Author Date Id Revision``.
 
 * Monitor python.org to make sure the PEP gets added to the site
   properly.
@@ -442,7 +434,7 @@ Once the PEP is ready for the repository, the PEP editor will:
   python-list & -dev).
 
 Updates to existing PEPs also come in to peps@python.org.  Many PEP
-authors are not SVN committers yet, so we do the commits for them.
+authors are not Python committers yet, so we do the commits for them.
 
 Many PEPs are written and maintained by developers with write access
 to the Python codebase.  The PEP editors monitor the python-checkins
@@ -455,25 +447,23 @@ relatively low volume.
 
 Resources:
 
-* `How Python is Developed <http://www.python.org/dev/intro/>`_
+* `Index of Python Enhancement Proposals <http://www.python.org/dev/peps/>`_
 
-* `Python's Development Process <http://www.python.org/dev/process/>`_
+* `Following Python's Development
+  <http://docs.python.org/devguide/communication.html>`_
 
-* `Why Develop Python? <http://www.python.org/dev/why/>`_
-
-* `Development Tools <http://www.python.org/dev/tools/>`_
+* `Python Developer's Guide <http://docs.python.org/devguide/>`_
 
 * `Frequently Asked Questions for Developers
-  <http://www.python.org/dev/faq/>`_
-
+  <http://docs.python.org/devguide/faq.html>`_
 
 References and Footnotes
 ========================
 
-.. [1] This historical record is available by the normal SVN commands
+.. [1] This historical record is available by the normal hg commands
    for retrieving older revisions.  For those without direct access to
-   the SVN tree, you can browse the current and past PEP revisions here:
-   http://svn.python.org/view/peps/trunk/
+   the hg repo, you can browse the current and past PEP revisions here:
+   http://hg.python.org/peps/
 
 .. [2] PEP 2, Procedure for Adding New Modules, Faassen
    (http://www.python.org/dev/peps/pep-0002)
@@ -485,8 +475,8 @@ References and Footnotes
    (http://www.python.org/dev/peps/pep-0012)
 
 .. [5] The script referred to here is pep2pyramid.py, the successor to
-   pep2html.py, both of which live in the same directory in the SVN
-   tree as the PEPs themselves.  Try ``pep2html.py --help`` for
+   pep2html.py, both of which live in the same directory in the hg
+   repo as the PEPs themselves.  Try ``pep2html.py --help`` for
    details.  The URL for viewing PEPs on the web is
    http://www.python.org/dev/peps/.