Update PEP VCS References. Point to the github repository.
This commit is contained in:
parent
ace74fca2a
commit
30784d4044
22
pep-0001.txt
22
pep-0001.txt
|
@ -152,18 +152,18 @@ not in keeping with the Python philosophy. The BDFL can be consulted
|
|||
during the approval phase, and is the final arbiter of the draft's
|
||||
PEP-ability.
|
||||
|
||||
Developers with hg push privileges for the `PEP repository`_ may claim
|
||||
Developers with git push privileges for the `PEP repository`_ may claim
|
||||
PEP numbers directly by creating and committing a new PEP. When doing so,
|
||||
the developer must handle the tasks that would normally be taken care of by
|
||||
the PEP editors (see `PEP Editor Responsibilities & Workflow`_). This
|
||||
includes ensuring the initial version meets the expected standards for
|
||||
submitting a PEP. Alternately, even developers may choose to submit PEPs
|
||||
through the PEP editors. When doing so, let the PEP editors know you have
|
||||
hg push privileges and they can guide you through the process of updating
|
||||
git push privileges and they can guide you through the process of updating
|
||||
the PEP repository directly.
|
||||
|
||||
As updates are necessary, the PEP author can check in new versions if they
|
||||
(or a collaborating developer) have hg push privileges, or else they can
|
||||
(or a collaborating developer) have git push privileges, or else they can
|
||||
email new PEP versions to the PEP editors for publication.
|
||||
|
||||
After a PEP number has been assigned, a draft PEP may be discussed further on
|
||||
|
@ -471,8 +471,8 @@ bug/patch to them, otherwise assign it to a PEP editor.
|
|||
When in doubt about where to send your changes, please check first
|
||||
with the PEP author and/or a PEP editor.
|
||||
|
||||
PEP authors with hg push privileges for the PEP repository can update the
|
||||
PEPs themselves by using "hg push" to submit their changes.
|
||||
PEP authors with git push privileges for the PEP repository can update the
|
||||
PEPs themselves by using "git push" to submit their changes.
|
||||
|
||||
|
||||
Transferring PEP Ownership
|
||||
|
@ -528,12 +528,12 @@ Once the PEP is ready for the repository, a PEP editor will:
|
|||
Python 3 only, the process is back to using numbers in the 100s again.
|
||||
Remember that numbers below 100 are meta-PEPs.)
|
||||
|
||||
* Add the PEP to a local clone of the PEP repository. For mercurial workflow
|
||||
* Add the PEP to a local clone of the PEP repository. For workflow
|
||||
instructions, follow `The Python Developers Guide <http://docs.python.org/devguide>`_
|
||||
|
||||
The mercurial repo for the peps is::
|
||||
The git repo for the peps is::
|
||||
|
||||
http://hg.python.org/peps/
|
||||
https://github.com/python/peps
|
||||
|
||||
* Run ``./genpepindex.py`` and ``./pep2html.py <PEP Number>`` to ensure they
|
||||
are generated without errors. If either triggers errors, then the web site
|
||||
|
@ -575,9 +575,9 @@ Resources:
|
|||
References and Footnotes
|
||||
========================
|
||||
|
||||
.. [1] This historical record is available by the normal hg commands
|
||||
.. [1] This historical record is available by the normal git commands
|
||||
for retrieving older revisions, and can also be browsed via HTTP here:
|
||||
http://hg.python.org/peps/
|
||||
https://github.com/python/peps
|
||||
|
||||
.. [2] PEP 2, Procedure for Adding New Modules, Faassen
|
||||
(http://www.python.org/dev/peps/pep-0002)
|
||||
|
@ -603,7 +603,7 @@ References and Footnotes
|
|||
|
||||
.. _Docutils: http://docutils.sourceforge.net/
|
||||
|
||||
.. _PEP repository: http://hg.python.org/peps
|
||||
.. _PEP repository: https://github.com/python/peps
|
||||
|
||||
|
||||
Copyright
|
||||
|
|
Loading…
Reference in New Issue