Get rid of the `Technical' PEP category. PEPs are either Standards
Track or Informational.
This commit is contained in:
parent
fcada696a2
commit
5ff3374dd9
12
pep-0001.txt
12
pep-0001.txt
|
@ -30,13 +30,11 @@ What is a PEP?
|
|||
|
||||
Kinds of PEPs
|
||||
|
||||
There are three kinds of PEPs. A standards track PEP describes a
|
||||
new feature for Python. An informational PEP describes a Python
|
||||
design issue, or provides general guidelines or information to the
|
||||
Python community, but does not propose a new feature. A technical
|
||||
PEP describes a new implementation or other internal modification
|
||||
that doesn't directly expose new features to the Python
|
||||
programmer.
|
||||
There are two kinds of PEPs. A standards track PEP describes a
|
||||
new feature or implementation for Python. An informational PEP
|
||||
describes a Python design issue, or provides general guidelines or
|
||||
information to the Python community, but does not propose a new
|
||||
feature.
|
||||
|
||||
|
||||
PEP Workflow
|
||||
|
|
Loading…
Reference in New Issue