Commit Graph

62 Commits

Author SHA1 Message Date
Jeremy Hylton 5b4565c9b8 Revise guidelines for discussion of PEP before draft exists. The goal
is to limit needless and uninformed discussion of an issue, not to
prevent all discussion.
2000-10-16 20:32:29 +00:00
Barry Warsaw 21d59a4d3b In order to get a PEP number, you need more than just an abstract.
You need a rough draft.
2000-08-23 15:58:05 +00:00
Barry Warsaw 5ff3374dd9 Get rid of the `Technical' PEP category. PEPs are either Standards
Track or Informational.
2000-08-23 05:04:42 +00:00
Barry Warsaw 11ff4a143f Add a link to the PEPs themselves in footnote 3, suggested by Peter
Schneider-Kamp.
2000-08-17 05:01:20 +00:00
Barry Warsaw ef6afbc490 Added a link to the SF CVSweb pages where the PEP histories can be
retrieved.
2000-08-17 03:11:08 +00:00
Barry Warsaw eac1680c48 Two typo corrections found by Terry Reedy. 2000-08-17 02:53:00 +00:00
Barry Warsaw 9fbbdf8f69 Added a second footnote with more information about the pep2html.py
script.
2000-08-15 05:54:18 +00:00
Barry Warsaw 269dd97ab2 There are now three basic types of PEPs: informational, standards
track, and technical.  The (new) latter type describes internal or
implementation changes that don't have a direct visible effect on the
Python language (e.g. Stackless).
2000-08-14 14:48:20 +00:00
Barry Warsaw 6f15dc67f4 Informational PEPs can also have a status of Active. 2000-08-08 02:30:55 +00:00
Barry Warsaw f4c64c9925 PEP proposals must have a title and an abstract. 2000-08-07 23:00:47 +00:00
Barry Warsaw 86fcb76ff6 Fleshed out the bulk of the guidelines, after internal discussion
among the PEP authors and the BDFL.
2000-07-25 17:59:08 +00:00
Barry Warsaw 41021a4bf9 Initial set of Python Enhancement Proposals 2000-07-13 06:33:08 +00:00