Nick Coghlan
6208fa0f9b
PEP 1: Move image to PEP root directory
2018-07-08 17:20:08 +10:00
Nick Coghlan
07dbec43dc
PEP 1: revert to PNG due to SVG rendering issues ( #702 )
2018-07-08 13:16:54 +10:00
Nick Coghlan
307dda38d4
PEP 1: Add a separate "Provisional" PEP status ( #577 )
...
This adds an explicit "Provisional" status for PEPs, making
it easier to track which PEPs are truly Final, and which
are pending further further public feedback based on
their initially published reference implementations.
2018-07-08 11:50:57 +10:00
Carol Willing
954708878f
PEP 1: Add a teachability section to suggested PEP content ( #652 )
2018-05-16 14:08:31 -04:00
Nick Coghlan
499a7c25c6
PEP 1: Remove legacy reference to pep2pyramid.py ( #626 )
...
This removes any reference to the technical details of online PEP
publication from PEP 1, replacing it with a reference to the
README in the PEP repository.
It also updates the README with relevant cross-references to the
pythondotorg project (based on some process pointers provided by
Mariatta Wijaya).
Resolves GH-575.
2018-04-27 18:21:50 +10:00
Nick Coghlan
a60ad1590c
PEP 1: Update some out of date details ( #576 )
...
- some interoperability specifications (e.g. the package index
download API) will never have a standard library implementation
- auxiliary files can go in a subdirectory
- PEP issues should be reported against the GitHub repo rather than
bugs.python.org
2018-04-21 16:42:53 +10:00
Mike Seplowitz
f0a3926c62
Fix rendering of editor's first initial ( #563 )
...
If R. David Murray's first initial is not escaped, it is interpreted as
the alphabetic ordinal in an enumerated list and rendered as
"18. David Murray".
2018-01-30 02:15:54 +11:00
Mariatta
cf3bad5ab3
Revert "Rename all .txt PEP files to .rst (GH-462)" (GH-464)
...
This reverts commit bb0e518ed3
.
2017-11-11 11:28:55 -08:00
Huang Huang
bb0e518ed3
Rename all .txt PEP files to .rst (GH-462)
...
For https://github.com/python/peps/issues/1
2017-11-11 10:30:43 -08:00
Oleg Broytman
9cd870ef71
Post-History should include dates of postings to python-ideas ( #441 )
...
Refs: https://mail.python.org/pipermail/python-dev/2017-October/149990.html
2017-10-27 14:49:30 -04:00
R. David Murray
0cfa95c9e9
Add myself as a PEP editor.
2017-09-05 14:47:48 -04:00
R. David Murray
62055aad79
Make Version/Last-Modified optional/deprecated.
...
These fields were maintained by the version control system, and this
no longer happens with git. They are already no longer displayed in
the published versions of the pages.
2017-09-05 14:41:25 -04:00
Mariatta
7b06cc339a
Use number 9999 in a draft PEP ( #234 )
...
Closes https://github.com/python/peps/issues/223
2017-04-12 10:27:15 -07:00
Yuri Broze
aa29454969
Incredibly minor typo fix in pep-0001 ( #181 )
...
"reference" -> "references"
2017-01-17 04:25:59 +11:00
Barry Warsaw
1cdddf8b00
Closes #38 ( #116 )
...
* Closes #38
* Updated workflow.
* Respond to review.
* s/clone/fork/
Use GitHub terminology rather than generic git terminology.
2016-10-15 14:38:43 +10:00
Barry Warsaw
6efb70f02a
Strongly prefer reStructuredText. ( #115 )
2016-10-14 20:33:28 +10:00
Senthil Kumaran
30784d4044
Update PEP VCS References. Point to the github repository.
2016-06-25 22:33:12 -07:00
Barry Warsaw
39ffb20dc3
PEP 9 (plaintext PEPs) is deprecated.
2016-01-05 18:33:02 -05:00
Berker Peksag
2acd07014c
Update PEP editors list.
2015-02-02 15:37:11 +02:00
Nick Coghlan
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
Nick Coghlan
a116485401
Eliminate some awkward phrasing (noted by Ezio Melloti)
2012-12-22 21:33:26 +10:00
Nick Coghlan
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
Barry Warsaw
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
Barry Warsaw
f5e3789b13
Spellchecked.
2012-05-17 06:53:13 -04:00
Nick Coghlan
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
Nick Coghlan
d9da11501a
Address Barry's comments and make a couple of other cleanups
2012-05-06 15:36:37 +10:00
Nick Coghlan
fcbc01ee45
Update PEP 1 to better reflect current practice
2012-05-05 22:56:57 +10:00
Guido van Rossum
40a8590b14
Clarify numbering scheme a bit more.
2012-03-12 17:06:44 -07:00
Brett Cannon
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
Éric Araujo
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
Senthil Kumaran
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
Benjamin Peterson
8e30bc931b
poke
2011-03-04 05:03:26 +00:00
Benjamin Peterson
8740ed3746
I'm going to call this superseded just to avoid collision in the key
2011-03-04 04:58:22 +00:00
Florent Xicluna
f31bacb1af
Remove reference to python-3000 mailing list in PEP1
2010-09-03 19:08:36 +00:00
Barry Warsaw
5d9da43a0a
Support the Resolution header, required for Standards Track PEPs.
2010-04-30 19:21:52 +00:00
Brett Cannon
12ff0d6e72
Clarify the current practices of how to develop a PEP.
2010-03-05 03:07:12 +00:00
Benjamin Peterson
c01c3dcf60
it seems release schedules are not process peps
2009-02-08 23:06:43 +00:00
Collin Winter
b3135ac7c5
Update PEP 1 to refer to the new bugs.python.org issue tracker.
2007-08-24 21:23:06 +00:00
Brett Cannon
8dc0e19ce5
Make Barry Warsaw's name consistent.
2007-06-28 19:53:41 +00:00
Brett Cannon
9fe45a32c3
Make all meta-PEPs be Process PEPs.
2007-06-19 04:52:34 +00:00
Brett Cannon
7eb1a2d8bb
Add the missing "Withdrawn" status as acceptable.
2007-06-19 04:26:23 +00:00
Georg Brandl
204b9762a8
Add a note about SVN keywords.
2007-05-01 19:53:12 +00:00
David Goodger
b08fe48dbf
spelling
2007-05-01 15:37:43 +00:00
David Goodger
7dcc069cd6
text tweak
2007-05-01 15:20:01 +00:00
David Goodger
bf6eef7fdb
added "PEP Editor Reponsibilities & Workflow" section
2007-05-01 04:00:51 +00:00
David Goodger
6967cb362c
changed CVS references to SVN; updated SVN viewing URL
2006-04-18 20:52:06 +00:00
David Goodger
663eabbe4a
added Auxiliary Files section; updated URLs; updated text file description
2006-03-24 03:24:04 +00:00
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