PEP 1: Add a teachability section to suggested PEP content (#652)
This commit is contained in:
parent
3445464c6a
commit
954708878f
|
@ -345,6 +345,15 @@ Each PEP should have the following parts:
|
||||||
appropriate for either the Python language reference or the
|
appropriate for either the Python language reference or the
|
||||||
standard library reference.
|
standard library reference.
|
||||||
|
|
||||||
|
9. How to Teach This -- For a PEP that adds new functionality or changes
|
||||||
|
language behavior, it is helpful to include a section on how to
|
||||||
|
teach users, new and experienced, how to apply the PEP to their
|
||||||
|
work.
|
||||||
|
|
||||||
|
This section may include key points and recommended documentation
|
||||||
|
changes that would help users adopt a new feature or migrate their
|
||||||
|
code to use a language change.
|
||||||
|
|
||||||
|
|
||||||
PEP Formats and Templates
|
PEP Formats and Templates
|
||||||
=========================
|
=========================
|
||||||
|
|
Loading…
Reference in New Issue