Barry Warsaw and I, the PEP editors, have been discussing the need for a new PEP
type lately. Martin von Löwis' PEP 347 was a prime example of a PEP that didn't
fit into the existing Standards Track and Informational categories. We agreed
upon a new "Process" PEP type. For more information, please see PEP 1
(http://www.python.org/peps/pep-0001.html) -- the type of which has also been
changed to Process.
Other good examples of Process PEPs are the release schedule PEPs, and I
understand there may be a new one soon.
(Please cc: any PEP-related mail to peps@python.org)
--
David Goodger <http://python.net/~goodger>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC/VO5rqIPjB1FxosR Av3wAJ9t4UTBDqa o+nlt1f64o+h+d9 1YbACgkvgH
jENyZ/nuH6v+qMczuE/sREo=
=AEq8
-----END PGP SIGNATURE-----
type lately. Martin von Löwis' PEP 347 was a prime example of a PEP that didn't
fit into the existing Standards Track and Informational categories. We agreed
upon a new "Process" PEP type. For more information, please see PEP 1
(http://www.python.org/peps/pep-0001.html) -- the type of which has also been
changed to Process.
Other good examples of Process PEPs are the release schedule PEPs, and I
understand there may be a new one soon.
(Please cc: any PEP-related mail to peps@python.org)
--
David Goodger <http://python.net/~goodger>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC/VO5rqIPjB1FxosR Av3wAJ9t4UTBDqa o+nlt1f64o+h+d9 1YbACgkvgH
jENyZ/nuH6v+qMczuE/sREo=
=AEq8
-----END PGP SIGNATURE-----