[Python-Dev] Rewriting PEP4 (original) (raw)
Barry Warsaw barry at python.org
Mon Dec 6 22:54:52 CET 2004
- Previous message: [Python-Dev] Rewriting PEP4
- Next message: [Python-Dev] Rewriting PEP4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2004-12-06 at 16:28, "Martin v. Löwis" wrote:
Martin, +1 on everything you wrote, with one minor quibble.
Removal ======= If the module has been deprecated for atleast a year and atleast a version, it can be removed. Removal should move it to old-libs for pure Python modules; a removal procedure for pure C modules has not been defined yet.
I wonder if the one year/one version rule is too short. Given that new versions come about every 18 months, I'd probably give it a 2 year/one version limit.
Modules that have currently deprecation messages in them often fail to identify the Python version in which removal will occur. For modules that have been deprecated since 2.1, I would suggest to remove them for 2.5, with the option of bringing them back in 2.5.1 if people complain
+1 here too.
-Barry
-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 307 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/python-dev/attachments/20041206/54057bcd/attachment.pgp
- Previous message: [Python-Dev] Rewriting PEP4
- Next message: [Python-Dev] Rewriting PEP4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]