This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aronacher
Recipients aronacher, bethard, eric.smith, gregory.p.smith, loewis, marklodato, michael.foord, ncoghlan, orsenthil, r.david.murray, rickysarraf
Date 2009-09-14.18:55:40
SpamBayes Score 1.51195e-07
Marked as misclassified No
Message-id <>
> I can respect that viewpoint. So what do you propose to do with
> existing modules like optparse that aren't required to make platform
> independent applications and are out of date and basically
> unmaintained? One option would be to remove them, but that's probably
> too drastic.

Documentation and a new kind of deprecation warning.  It's
documentation-deprecated in one version, one later a real deprecation
warning appears that sticks around for a couple of versions.  The
documentation would explain how to hide the deprecation warning and
tells the user to better use more modern alternatives.

This of course requires packaging to work flawlessly first which I
consider to be high priority.
Date User Action Args
2009-09-14 18:55:42aronachersetrecipients: + aronacher, loewis, gregory.p.smith, ncoghlan, orsenthil, bethard, eric.smith, r.david.murray, michael.foord, rickysarraf, marklodato
2009-09-14 18:55:42aronachersetmessageid: <>
2009-09-14 18:55:40aronacherlinkissue6247 messages
2009-09-14 18:55:40aronachercreate