Skip to content

Commit 05bc9ae

Browse files
committed
Meta: Further revise PEP change guidance to reflect current reality
1 parent b93cb98 commit 05bc9ae

File tree

2 files changed

+11
-9
lines changed

2 files changed

+11
-9
lines changed

CONTRIBUTING.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,10 @@ or may not be appropriate, depending on the PEP's status. See `PEP 1
2828
<https://www.python.org/dev/peps/pep-0001/#pep-maintenance>`__ for more.
2929

3030
Copyediting and proofreading Draft and Active PEPs (including fixing spelling
31-
and formatting issues) is welcomed, and can be done via pull request to this
32-
repo, though we generally advise against PRs that simply mass-correct minor
33-
typos on older PEPs which don't significantly impair meaning and understanding.
31+
and formatting issues) is welcomed (subject to review by the PEP authors),
32+
and can be done via pull request to this repo, though we generally advise
33+
against PRs that simply mass-correct minor typos on older PEPs which don't
34+
significantly impair meaning and understanding.
3435
Substantive content changes should first be proposed on PEP discussion threads.
3536

3637
If you're still unsure, we encourage you to reach out first before opening a

pep-0001.txt

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -459,15 +459,15 @@ PEP Maintenance
459459
---------------
460460

461461
In general, PEPs are no longer substantially modified after they have reached
462-
the Final, Rejected or Superseded state. Once a PEP has been completed,
463-
it is considered to be a historical document rather than living specifications.
462+
the Accepted, Final, Rejected or Superseded state. Once resolution is reached,
463+
a PEP is considered a historical document rather than a living specification.
464464
Formal documentation of the expected behavior should be maintained elsewhere,
465465
such as the `Language Reference`_ for core features, the `Library Reference`_
466466
for standard library modules or the `PyPA Specifications`_ for packaging.
467467

468468
If changes based on implementation experience and user feedback are made to
469-
Standards track PEPs while in the Accepted or Provisional state, they
470-
should be noted in the PEP, such that the PEP accurately describes the state of
469+
Standards track PEPs while in the Provisional or (with SC approval) Accepted
470+
state, they should be noted in the PEP, such that the PEP accurately describes
471471
the implementation at the point where it is marked Final.
472472

473473
Active Informational and Process PEPs may be updated over time to reflect
@@ -476,8 +476,9 @@ followed in these cases will depend on the nature and purpose of the PEP
476476
being updated. Substantive changes to governance PEPs must be reviewed by the
477477
Steering Council (by opening a `Steering Council issue`_).
478478

479-
Draft PEPs are freely open for discussion and proposed modification until
480-
submitted to the Steering Council or PEP-Delegate for review and resolution.
479+
Draft PEPs are freely open for discussion and proposed modification,
480+
at the discretion of the authors, until submitted to the
481+
Steering Council or PEP-Delegate for review and resolution.
481482
Substantive content changes should generally be first proposed on
482483
the PEP's discussion thread listed in its ``Discussions-To`` header.
483484
Occasionally, a Deferred or even a Withdrawn PEP may be resurrected

0 commit comments

Comments
 (0)