Skip to content

PEP 1: Suggest people reach out to important projects to support their PEP's motivation #1842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brettcannon merged 2 commits into from
Mar 1, 2021
Merged

PEP 1: Suggest people reach out to important projects to support their PEP's motivation #1842

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
63eeec2
Suggest people reach out to important projects to support their PEP's…
brettcannon Feb 26, 2021
8e4c371
Update pep-0001.txt
brettcannon Mar 1, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 15 additions & 8 deletions pep-0001.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,12 +94,12 @@ the currently active Python core team members described in PEP 13 [5]_.
Python's BDFL
-------------

Previous versions of this PEP used the title "BDFL-Delegate" for PEP decision makers. This was
a historical reference to Python's previous governance model, where all design
authority ultimately derived from Guido van Rossum, the original creator of the
Python programming language. By contrast, the Steering Council's design
authority derives from their election by the currently active core developers.
Now, PEP-Delegate is used in place of BDFL-Delegate.
Previous versions of this PEP used the title "BDFL-Delegate" for PEP decision
makers. This was a historical reference to Python's previous governance model,
where all design authority ultimately derived from Guido van Rossum, the
original creator of the Python programming language. By contrast, the Steering
Council's design authority derives from their election by the currently active
core developers. Now, PEP-Delegate is used in place of BDFL-Delegate.


PEP Editors
Expand Down Expand Up @@ -421,8 +421,10 @@ Each PEP should have the following parts/sections:
3. Motivation -- The motivation is critical for PEPs that want to
change the Python language, library, or ecosystem. It should
clearly explain why the existing language specification is
inadequate to address the problem that the PEP solves. PEP
submissions without sufficient motivation may be rejected outright.
inadequate to address the problem that the PEP solves. This can
include collecting documented support for the PEP from important
projects in the Python ecosystem. PEP submissions without
sufficient motivation may be rejected.

4. Rationale -- The rationale fleshes out the specification by
describing why particular design decisions were made. It should
Expand Down Expand Up @@ -694,6 +696,11 @@ For each new PEP that comes in an editor does the following:
PEP 8 & PEP 7). Editors may correct problems themselves, but are
not required to do so. (Text format is checked by Travis CI.)

* If a project is portrayed as benefiting from or supporting the PEP, make sure
there is some direct indication from the project included to make the support
clear. This is to avoid a PEP accidentally portraying a project as supporting
a PEP when in fact the support is based on conjecture.

If the PEP isn't ready, an editor will send it back to the author for
revision, with specific instructions. If reST formatting is a
problem, ask the author(s) to use PEP 12 as a template and resubmit.
Expand Down