9a5ae7dfc2
Clarify some style points, such as fill column, double-spacing at the
...
end of sentences, etc. Add a reference to PEP 9, a new sample PEP
template.
2001-08-14 23:58:09 +00:00
3d503a4ea4
Clarification on when and how to report PEP bugs and updates.
2001-08-14 22:48:14 +00:00
85c2313552
Add a Last-Modified: header.
...
Add a short description of the format for both the Author: and
Post-History: headers.
Elaborate a bit about how and where PEP discussions should be held.
2001-08-14 22:04:52 +00:00
d01aa72709
Because of the redesign of PEP 0, titles can now be of a maximum 44
...
characters in length (up from the previous 38). I think this still
gives us plenty of room for the owner fields.
2001-08-14 16:48:57 +00:00
295e210393
barry@digicool.com => barry@zope.com
2001-08-14 15:45:26 +00:00
48de44832b
Update email address
2001-08-01 20:11:56 +00:00
633cc715aa
In PEP style section, describe how to refer to URLs and PEPs in the
...
body of a PEP document. Also describe how to refer to PEP in the
References sections, including the use of www.python.org/peps as the
preferred link.
Added a section on reporting bugs and submitting patches w.r.t. PEPs.
2001-07-05 18:52:25 +00:00
e7232264a6
PEP Style section: allow optional Last-Modified: header to hold the
...
RCS $Date$ revision string.
2001-06-06 05:57:22 +00:00
4bf3609ebc
Added Requires: header.
2001-03-28 20:06:10 +00:00
1d573c6465
Add a note that titles should be limited to 38 characters.
2001-03-28 19:52:13 +00:00
ea8b327a2f
Terry Reedy points out the inconsistency of PEP 1's status. :)
2001-03-21 21:52:08 +00:00
33edbc7212
Status: can now also be "Replaced" (thanks AMK).
2001-03-21 17:20:29 +00:00
7ce8ba5d99
Some updates based on feedback from PEP authors. Also, this applies
...
SF patch #410223 by Andrew Kuchling, describing the new Replaces: and
Replaced-by: headers.
2001-03-21 17:05:27 +00:00
63570042bf
It's "barry" now, not "bwarsaw"...
2000-10-30 21:16:38 +00:00
ceba1877b2
Update a few email addresses.
2000-10-30 20:48:44 +00:00
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
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
5ff3374dd9
Get rid of the `Technical' PEP category. PEPs are either Standards
...
Track or Informational.
2000-08-23 05:04:42 +00:00
11ff4a143f
Add a link to the PEPs themselves in footnote 3, suggested by Peter
...
Schneider-Kamp.
2000-08-17 05:01:20 +00:00
ef6afbc490
Added a link to the SF CVSweb pages where the PEP histories can be
...
retrieved.
2000-08-17 03:11:08 +00:00
eac1680c48
Two typo corrections found by Terry Reedy.
2000-08-17 02:53:00 +00:00
9fbbdf8f69
Added a second footnote with more information about the pep2html.py
...
script.
2000-08-15 05:54:18 +00:00
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
6f15dc67f4
Informational PEPs can also have a status of Active.
2000-08-08 02:30:55 +00:00
f4c64c9925
PEP proposals must have a title and an abstract.
2000-08-07 23:00:47 +00:00
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
41021a4bf9
Initial set of Python Enhancement Proposals
2000-07-13 06:33:08 +00:00
Barry Warsaw
Jeremy Hylton
unknown
Fred Drake