We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 9fa0112 commit 657615eCopy full SHA for 657615e
1 file changed
developer-workflow/lang-changes.rst
@@ -69,13 +69,14 @@ code.
69
70
Some things you should **not** do:
71
72
-- **Don't** format your idea as a PEP. It's good to use the PEP template as a
+- **Don't** format your idea as a Python Enhancement Proposal (*PEP*).
73
+ It's good to use the PEP template as a
74
guide for what information to include, but don't try to write a full PEP
75
until the idea has been accepted for further consideration.
76
77
- **Don't** create a list of proposed changes. Each idea needs its own
78
discussion. Proposing a change is significant work. You will need to spend
- time on each proposal.
79
+ time on each proposal. A tossed-off list will not be taken seriously.
80
81
When justifying your idea, these are not good reasons to make a change:
82
0 commit comments