iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
7,807 Commits 2 Branches 2 Tags 68 MiB
Commit Graph

99 Commits

Author SHA1 Message Date
David Goodger 794b1f8f11 converted to UTF-8 & added coding slugs 2006-03-02 19:54:50 +00:00
David Goodger e78fb66230 Process PEPs may also be Active 2005-08-13 18:01:01 +00:00
David Goodger 1d255cd68b fixed idiom 2005-08-13 01:42:17 +00:00
David Goodger 7435767028 added new Process PEP type 2005-08-13 01:37:32 +00:00
David Goodger 8d042dd201 clarifications 2004-08-27 21:19:48 +00:00
David Goodger 5591215fe0 updated 2004-07-16 19:27:23 +00:00
Greg Ward 8e71b3cd7b Grammar fix. 2003-05-07 00:03:13 +00:00
David Goodger 0a690292ff converted to reStructuredText 2003-05-03 16:01:32 +00:00
David Goodger 7361fd0b50 add proactive review power for BDFL; add a description of acceptance criteria; and take some credit ;-) 2003-05-02 21:34:44 +00:00
David Goodger 8c85881454 corrected URL 2002-11-08 04:48:16 +00:00
David Goodger 3906d98f25 updated 2002-11-06 05:38:56 +00:00
Barry Warsaw 0e36409f13 David Goodger writes: 
* Changed the "PEP Template" section to "PEP Formats and Templates",
  in which plaintext and reStructuredText PEPs are described.

* Added "PEP Header Preamble" heading, for the RFC 2822 header
  description.

  - Rearranged some descriptions to match the header order.
  - Removed the colons from header field names (e.g., "the Author
    header").
  - Added a description of the Content-Type header.

* Moved the plaintext-PEP-specific "PEP Formatting Requirements"
  section to PEP 9.  PEP 1 now deals only with content, not format.

* Minor edits, including:

  - Capitalized "Standards Track" and "Informational" throughout.
  - In "it's not like such decisions can be reversed", "can" should be
    "can't"; fixed.
 2002-08-26 16:19:25 +00:00
Barry Warsaw 4a805d3603 Based on feedback inspired by Francois Pinard, we're changing the 
format of the Author: header to be "Random J. User <address@dom.ain>"

Update PEP 1 style guidelines.

Updated PEP 9 template.

Updated PEP 0 as an example.
 2002-07-30 16:23:15 +00:00
Barry Warsaw 888748d8c8 Some clarifications about what should go in a successful PEP, as well 
as cause for rejection of pre-PEPs.
 2002-07-29 18:34:59 +00:00
Barry Warsaw 83614f97e5 Addeda paragraph about transferring ownership of the PEP. 2002-07-12 16:39:49 +00:00
Barry Warsaw 732c0ece30 Remove Barry's & Jeremy's email address from the Authors: header (note 
to other PEP authors -- it is okay now to omit your email address from
this header, although we will be obscuring it soon).

Also, use peps@python.org as the PEP editor contact address instead of
Barry's personal address.

Remove Guido's email address.

Other updates explaining where address obscuring takes place and where
it doesn't.

Updated the Emacs file local variable section.
 2002-05-28 15:20:17 +00:00
Andrew M. Kuchling 98315482b7 Change "not" -> "not necessarily" as Jeremy suggested 
Fix typo
 2002-04-18 19:19:35 +00:00
Andrew M. Kuchling bf5099b6b6 Clarify significance of informational PEPs 2002-04-18 16:27:07 +00:00
Fred Drake 529701291f Update PEP URLs to prefer www.python.org. 2002-04-05 19:42:56 +00:00
Barry Warsaw 6644dcee69 Add a note about how PEPs should really be more focussed, and contain 
a single core idea.
 2002-04-02 03:20:07 +00:00
Barry Warsaw d9736b39aa Last-Modified: is now a required header. 2002-03-01 00:42:48 +00:00
Barry Warsaw 0d68c2e31e Add a bit of information to descript the pep2html.py process. 2001-11-12 14:57:18 +00:00
Barry Warsaw 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
Barry Warsaw 3d503a4ea4 Clarification on when and how to report PEP bugs and updates. 2001-08-14 22:48:14 +00:00
Barry Warsaw 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
Barry Warsaw 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
Barry Warsaw 295e210393 barry@digicool.com => barry@zope.com 2001-08-14 15:45:26 +00:00
Jeremy Hylton 48de44832b Update email address 2001-08-01 20:11:56 +00:00
Barry Warsaw 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
unknown e7232264a6 PEP Style section: allow optional Last-Modified: header to hold the 
RCS $Date$ revision string.
 2001-06-06 05:57:22 +00:00
Barry Warsaw 4bf3609ebc Added Requires: header. 2001-03-28 20:06:10 +00:00
Barry Warsaw 1d573c6465 Add a note that titles should be limited to 38 characters. 2001-03-28 19:52:13 +00:00
Barry Warsaw ea8b327a2f Terry Reedy points out the inconsistency of PEP 1's status. :) 2001-03-21 21:52:08 +00:00
Barry Warsaw 33edbc7212 Status: can now also be "Replaced" (thanks AMK). 2001-03-21 17:20:29 +00:00
Barry Warsaw 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
Fred Drake 63570042bf It's "barry" now, not "bwarsaw"... 2000-10-30 21:16:38 +00:00
Fred Drake ceba1877b2 Update a few email addresses. 2000-10-30 20:48:44 +00:00
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