Mark PEP 102 as replaced, and add a rationale.
This commit is contained in:
parent
bd1684b453
commit
b91b364be9
12
pep-0102.txt
12
pep-0102.txt
|
@ -5,10 +5,20 @@ Last-Modified: $Date$
|
||||||
Author: anthony@interlink.com.au (Anthony Baxter),
|
Author: anthony@interlink.com.au (Anthony Baxter),
|
||||||
barry@python.org (Barry Warsaw),
|
barry@python.org (Barry Warsaw),
|
||||||
guido@python.org (Guido van Rossum)
|
guido@python.org (Guido van Rossum)
|
||||||
Status: Active
|
Status: Replaced
|
||||||
Type: Informational
|
Type: Informational
|
||||||
Created: 22-Aug-2001 (edited down on 9-Jan-2002 to become PEP 102)
|
Created: 22-Aug-2001 (edited down on 9-Jan-2002 to become PEP 102)
|
||||||
Post-History:
|
Post-History:
|
||||||
|
Replaced-By: 101
|
||||||
|
|
||||||
|
|
||||||
|
Replacement Note
|
||||||
|
|
||||||
|
Although the size of the to-do list in this PEP is much less scary
|
||||||
|
than that in PEP 101, it turns out not to be enough justification
|
||||||
|
for the duplication of information, and with it, the danger of one
|
||||||
|
of the copies to become out of date. Therefore, this PEP is not
|
||||||
|
maintained anymore, and micro releases are fully covered by PEP 101.
|
||||||
|
|
||||||
|
|
||||||
Abstract
|
Abstract
|
||||||
|
|
Loading…
Reference in New Issue