Update PEP 1 to refer to the new bugs.python.org issue tracker.
This commit is contained in:
parent
fb6c09e47b
commit
b3135ac7c5
20
pep-0001.txt
20
pep-0001.txt
|
@ -80,8 +80,7 @@ ascertain whether the idea is PEP-able. Posting to the
|
|||
comp.lang.python newsgroup (a.k.a. python-list@python.org mailing
|
||||
list) is recommended. Small enhancements or patches often don't need
|
||||
a PEP and can be injected into the Python development work flow with a
|
||||
patch submission to the SourceForge `patch manager`_ or `feature
|
||||
request tracker`_.
|
||||
patch submission to the Python `issue tracker`_.
|
||||
|
||||
The PEP champion then emails the PEP editor <peps@python.org> with a
|
||||
proposed title and a rough, but fleshed out, draft of the PEP. This
|
||||
|
@ -343,15 +342,14 @@ factors, such as the maturity of the PEP, the preferences of the PEP
|
|||
author, and the nature of your comments. For the early draft stages
|
||||
of the PEP, it's probably best to send your comments and changes
|
||||
directly to the PEP author. For more mature, or finished PEPs you may
|
||||
want to submit corrections to the SourceForge `bug manager`_ or better
|
||||
yet, the SourceForge `patch manager`_ so that your changes don't get
|
||||
lost. If the PEP author is a SourceForge developer, assign the
|
||||
want to submit corrections to the Python `issue tracker`_ so that your
|
||||
changes don't get lost. If the PEP author is a Python developer, assign the
|
||||
bug/patch to him, otherwise assign it to the PEP editor.
|
||||
|
||||
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
|
||||
PEP authors who are also Python committers can update the
|
||||
PEPs themselves by using "svn commit" to commit their changes.
|
||||
|
||||
|
||||
|
@ -476,11 +474,8 @@ References and Footnotes
|
|||
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
|
||||
|
||||
.. _feature request tracker:
|
||||
http://sourceforge.net/tracker/?atid=355470&group_id=5470&func=browse
|
||||
.. _issue tracker:
|
||||
http://bugs.python.org/
|
||||
|
||||
.. _Open Publication License: http://www.opencontent.org/openpub/
|
||||
|
||||
|
@ -488,9 +483,6 @@ References and Footnotes
|
|||
|
||||
.. _Docutils: http://docutils.sourceforge.net/
|
||||
|
||||
.. _bug manager:
|
||||
http://sourceforge.net/tracker/?group_id=5470&atid=105470
|
||||
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
|
Loading…
Reference in New Issue