Skip to content

PEP 387: Update language around discussion venues, part 2 #4770

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
hugovk merged 3 commits into from
Jan 15, 2026
Merged

PEP 387: Update language around discussion venues, part 2 #4770

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1ee67bc
PEP 387: Update language around discussion venues, part 2
hugovk Jan 6, 2026
a7359f9
PEP 387: Link to PEP 1 rather than a section
hugovk Jan 6, 2026
0e73ec0
Improve wording
hugovk Jan 6, 2026
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
8 changes: 6 additions & 2 deletions peps/pep-0387.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,8 +146,12 @@ Making Incompatible Changes
Making an incompatible change is a gradual process performed over
several releases:

1. :pep:`PEP 1: Start with an idea <1#start-with-an-idea-for-python>` discussion.
If the discussion reaches consensus that acceptance is possible a PEP or
1. Discuss the change.
Depending on the degree of incompatibility, this could be on
`Discourse <https://discuss.python.org/>`__,
the `issue tracker <https://github.com/python/cpython/issues/>`__,
or the appropriate workgroup or SIG.
If the discussion reaches consensus a :pep:`PEP <1>` or
similar document may be written.
Hopefully users of the affected API will pipe up to comment.

Expand Down