30784d4044
Update PEP VCS References. Point to the github repository.
2016-06-25 22:33:12 -07:00
39ffb20dc3
PEP 9 (plaintext PEPs) is deprecated.
2016-01-05 18:33:02 -05:00
2acd07014c
Update PEP editors list.
2015-02-02 15:37:11 +02:00
8122474fe8
PEP process changes triggered by the packaging PEPs
...
- allow a Discussion-To header to indicate the list for pronouncement
- allow version independent Standards track PEPs
2013-04-07 18:26:06 +10:00
a116485401
Eliminate some awkward phrasing (noted by Ezio Melloti)
2012-12-22 21:33:26 +10:00
2af18441e8
Further updates to PEP 1 to better reflect current practice
...
- identify the current PEP editors and clarify their role
- separate out PEP administrative email from design discussion
- reference implementations typically co-evolve with their PEP
- it's OK to get a PEP number before a PEP is ready for python-dev
- eliminate most of the ambiguous 'we' references
(Initial patch by Chris Jerdonek)
2012-12-22 21:30:14 +10:00
2a95453d84
Make it clear that the PEP editors can only review a completed PEP for
...
style and consistency. The BDFL (by way of python-dev) is the final
arbiter of the PEP for its acceptance into the language.
2012-05-18 10:08:09 -04:00
f5e3789b13
Spellchecked.
2012-05-17 06:53:13 -04:00
73310d4468
Add the BDFL-Delegate field, using myself as the test case.
...
Including the delegate's email address would be nice, but the PEP writer lives in docutils upstream rather than our PEPs repo and I'm not updating docutils just to mask an additional field, nor am I inclined to figure out how to move the writer definition downstream where it belongs
2012-05-06 16:31:52 +10:00
d9da11501a
Address Barry's comments and make a couple of other cleanups
2012-05-06 15:36:37 +10:00
fcbc01ee45
Update PEP 1 to better reflect current practice
2012-05-05 22:56:57 +10:00
40a8590b14
Clarify numbering scheme a bit more.
2012-03-12 17:06:44 -07:00
0d4547ba0a
Be explicit about using the lowest PEP number (e.g. in the 400s) instead of the next number (e.g. in the 3100s).
2012-03-12 19:22:35 -04:00
ea9bdcad6a
Remove strange wording.
...
(“direct access” to the hg repo uses the same protocol than public
browsing, so the distinction does not make sense anymore.)
2012-02-29 07:29:36 +01:00
42303d9a9a
Fix broken links in pep-0001.txt. Update the information with pointers to hg
...
and devguide.
2011-10-06 22:38:55 +08:00
8e30bc931b
poke
2011-03-04 05:03:26 +00:00
8740ed3746
I'm going to call this superseded just to avoid collision in the key
2011-03-04 04:58:22 +00:00
f31bacb1af
Remove reference to python-3000 mailing list in PEP1
2010-09-03 19:08:36 +00:00
5d9da43a0a
Support the Resolution header, required for Standards Track PEPs.
2010-04-30 19:21:52 +00:00
12ff0d6e72
Clarify the current practices of how to develop a PEP.
2010-03-05 03:07:12 +00:00
c01c3dcf60
it seems release schedules are not process peps
2009-02-08 23:06:43 +00:00
b3135ac7c5
Update PEP 1 to refer to the new bugs.python.org issue tracker.
2007-08-24 21:23:06 +00:00
8dc0e19ce5
Make Barry Warsaw's name consistent.
2007-06-28 19:53:41 +00:00
9fe45a32c3
Make all meta-PEPs be Process PEPs.
2007-06-19 04:52:34 +00:00
7eb1a2d8bb
Add the missing "Withdrawn" status as acceptable.
2007-06-19 04:26:23 +00:00
204b9762a8
Add a note about SVN keywords.
2007-05-01 19:53:12 +00:00
b08fe48dbf
spelling
2007-05-01 15:37:43 +00:00
7dcc069cd6
text tweak
2007-05-01 15:20:01 +00:00
bf6eef7fdb
added "PEP Editor Reponsibilities & Workflow" section
2007-05-01 04:00:51 +00:00
6967cb362c
changed CVS references to SVN; updated SVN viewing URL
2006-04-18 20:52:06 +00:00
663eabbe4a
added Auxiliary Files section; updated URLs; updated text file description
2006-03-24 03:24:04 +00:00
794b1f8f11
converted to UTF-8 & added coding slugs
2006-03-02 19:54:50 +00:00
e78fb66230
Process PEPs may also be Active
2005-08-13 18:01:01 +00:00
1d255cd68b
fixed idiom
2005-08-13 01:42:17 +00:00
7435767028
added new Process PEP type
2005-08-13 01:37:32 +00:00
8d042dd201
clarifications
2004-08-27 21:19:48 +00:00
5591215fe0
updated
2004-07-16 19:27:23 +00:00
8e71b3cd7b
Grammar fix.
2003-05-07 00:03:13 +00:00
0a690292ff
converted to reStructuredText
2003-05-03 16:01:32 +00:00
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
8c85881454
corrected URL
2002-11-08 04:48:16 +00:00
3906d98f25
updated
2002-11-06 05:38:56 +00:00
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
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
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
83614f97e5
Addeda paragraph about transferring ownership of the PEP.
2002-07-12 16:39:49 +00:00
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
98315482b7
Change "not" -> "not necessarily" as Jeremy suggested
...
Fix typo
2002-04-18 19:19:35 +00:00
bf5099b6b6
Clarify significance of informational PEPs
2002-04-18 16:27:07 +00:00
529701291f
Update PEP URLs to prefer www.python.org.
2002-04-05 19:42:56 +00:00
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
d9736b39aa
Last-Modified: is now a required header.
2002-03-01 00:42:48 +00:00
0d68c2e31e
Add a bit of information to descript the pep2html.py process.
2001-11-12 14:57:18 +00:00
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
Senthil Kumaran
Barry Warsaw
Berker Peksag
Nick Coghlan
Guido van Rossum
Brett Cannon
Éric Araujo
Benjamin Peterson
Florent Xicluna
Brett Cannon
Collin Winter
Georg Brandl
David Goodger
Greg Ward
Andrew M. Kuchling
Fred Drake
Jeremy Hylton
unknown