-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 P.J. Eby wrote:
> Just a reminder: I'm planning to actually update PEP 333 over the > weekend and start working on wsgiref updates, so if you have any > last-minute comments on the proposal, now's the time to post them, > however unpolished they may be! I'm fine with the substance of the changes you proposed, but puzzled about the process: in what case does it work to updated an already-approved-and-implemented PEP would be updated, instead of replacing it with a newer PEP (e.g., PEPs 241 -> 314 -> 345). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkybob0ACgkQ+gerLs4ltQ64eACfedK0bHE9/zTpwx5acmXlJi+0 sKAAoL8Q3V2tPnmC4A9BBwb088odHSqf =f0ph -----END PGP SIGNATURE----- _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com