-
Notifications
You must be signed in to change notification settings - Fork 514
BRython Enhancement Proposals (BREPs)
kikocorreoso edited this page Oct 31, 2014
·
3 revisions
See Python's Enhancement Proposals for instructions of how BREPs should be structured.
Meta-PEPs (PEPs about PEPs or Processes) | |||
---|---|---|---|
Key | num | title | owner |
P | [1] | PEP purpose and guidelines | Warsaw, Hylton, Goodger, Coghlan |
P | [2] | Bug fix releases | --- |
P | [3] | Style guide for Python code | --- |
P | [4] | Style guide for Javascript code | --- |
P | [5] | Voting guidelines | --- |
P | [6] | Removing support for little used platforms | --- |
Other Informational PEPs | |||
---|---|---|---|
Key | num | title | owner |
Accepted PEPs (accepted; may not be implemented yet) | |||
---|---|---|---|
Key | num | title | owner |
Open PEPs (under consideration) | |||
---|---|---|---|
Key | num | title | owner |
Finished PEPs (done, implemented in code repository) | |||
---|---|---|---|
Key | num | title | owner |
Abandoned, Withdrawn, and Rejected PEPs | |||
---|---|---|---|
Key | num | title | owner |
S - Standards Track BREP
I - Informational BREP
P - Process BREP
A - Accepted proposal
R - Rejected proposal
W - Withdrawn proposal
D - Deferred proposal
F - Final proposal
A - Active proposal
D - Draft proposal
S - Superseded proposal