iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

it seems release schedules are not process peps

This commit is contained in:
Benjamin Peterson 2009-02-08 23:06:43 +00:00
parent 8e854fa4af
commit c01c3dcf60
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0001.txt
View File

@ -51,10 +51,10 @@ There are three kinds of PEP:
language itself. They may propose an implementation, but not to
Python's codebase; they often require community consensus; unlike
Informational PEPs, they are more than recommendations, and users
are typically not free to ignore them. Examples include release
schedules, procedures, guidelines, changes to the decision-making
process, and changes to the tools or environment used in Python
development. Any meta-PEP is also considered a Process PEP.
are typically not free to ignore them. Examples include
procedures, guidelines, changes to the decision-making process, and
changes to the tools or environment used in Python development.
Any meta-PEP is also considered a Process PEP.
PEP Work Flow