changed CVS references to SVN; updated SVN viewing URL
This commit is contained in:
parent
453a6c7d77
commit
6967cb362c
34
pep-0001.txt
34
pep-0001.txt
|
@ -104,7 +104,7 @@ community at large, and improve the PEP for re-submission.
|
|||
The author of the PEP is then responsible for posting the PEP to the
|
||||
community forums, and marshaling community support for it. As updates
|
||||
are necessary, the PEP author can check in new versions if they have
|
||||
CVS commit permissions, or can email new PEP versions to the PEP
|
||||
SVN commit permissions, or can email new PEP versions to the PEP
|
||||
editor for committing.
|
||||
|
||||
Standards Track PEPs consist of two parts, a design document and a
|
||||
|
@ -255,8 +255,8 @@ optional and are described below. All other headers are required. ::
|
|||
|
||||
PEP: <pep number>
|
||||
Title: <pep title>
|
||||
Version: <cvs version string>
|
||||
Last-Modified: <cvs date string>
|
||||
Version: <svn version string>
|
||||
Last-Modified: <svn date string>
|
||||
Author: <list of authors' real names and optionally, email addrs>
|
||||
* Discussions-To: <email address>
|
||||
Status: <Draft | Active | Accepted | Deferred | Rejected |
|
||||
|
@ -351,17 +351,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/SourceForge committers can update the
|
||||
PEPs themselves by using "cvs commit" to commit their changes. PEP
|
||||
authors with python.org access should also remember to push the
|
||||
formatted PEP text out to the web by doing the following::
|
||||
|
||||
% python pep2html.py -i NUM
|
||||
|
||||
where NUM is the number of the PEP you want to push out. See ::
|
||||
|
||||
% python pep2html.py --help
|
||||
|
||||
for details.
|
||||
PEPs themselves by using "svn commit" to commit their changes.
|
||||
|
||||
|
||||
Transferring PEP Ownership
|
||||
|
@ -388,11 +378,10 @@ decision (it's not like such decisions can't be reversed :).
|
|||
References and Footnotes
|
||||
========================
|
||||
|
||||
.. [1] This historical record is available by the normal CVS commands
|
||||
.. [1] This historical record is available by the normal SVN commands
|
||||
for retrieving older revisions. For those without direct access to
|
||||
the CVS tree, you can browse the current and past PEP revisions via
|
||||
the SourceForge web site at
|
||||
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/nondist/peps/
|
||||
the SVN tree, you can browse the current and past PEP revisions here:
|
||||
http://svn.python.org/view/peps/trunk/
|
||||
|
||||
.. [2] PEP 2, Procedure for Adding New Modules, Faassen
|
||||
(http://www.python.org/dev/peps/pep-0002)
|
||||
|
@ -403,10 +392,11 @@ References and Footnotes
|
|||
.. [4] PEP 12, Sample reStructuredText PEP Template, Goodger, Warsaw
|
||||
(http://www.python.org/dev/peps/pep-0012)
|
||||
|
||||
.. [5] The script referred to here is pep2html.py, which lives in the
|
||||
same directory in the CVS tree 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/.
|
||||
.. [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
|
||||
details. The URL for viewing PEPs on the web is
|
||||
http://www.python.org/dev/peps/.
|
||||
|
||||
.. _patch manager:
|
||||
http://sourceforge.net/tracker/?group_id=5470&atid=305470
|
||||
|
|
Loading…
Reference in New Issue