iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 1: Refer to GitHub for the Python issue tracker (#2568) 

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
Co-authored-by: Chris Angelico <rosuav@gmail.com>
This commit is contained in:
Itamar Ostricher 2022-05-02 16:57:13 -07:00 committed by GitHub
parent 278070ac97
commit 4b04a2b7be
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pep-0001.txt
View File

@ -123,10 +123,10 @@ Start with an idea for Python
The PEP process begins with a new idea for Python. It is highly
recommended that a single PEP contain a single key proposal or new
idea. Small enhancements or patches often don't need
a PEP and can be injected into the Python development workflow with a
patch submission to the Python `issue tracker`_. The more focused the
PEP, the more successful it tends to be. The PEP editors reserve the
idea; the more focused the PEP, the more successful it tends to be.
Most enhancements and bug fixes don't need a PEP and
can be submitted directly to the `Python issue tracker`_.
The PEP editors reserve the
right to reject PEP proposals if they appear too unfocused or too
broad. If in doubt, split your PEP into several well-focused ones.
@ -834,7 +834,7 @@ Footnotes
.. _.github/CODEOWNERS: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
.. _issue tracker: https://bugs.python.org/
.. _Python issue tracker: https://github.com/python/cpython/issues
.. _CC0-1.0-Universal: https://choosealicense.com/licenses/cc0-1.0/