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 serhiy.storchaka
Recipients John Hagen, SilentGhost, martin.panter, matrixise, r.david.murray, serhiy.storchaka
Date 2015-11-01.15:48:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446392894.13.0.000960147917143.issue25521@psf.upfronthosting.co.za>
In-reply-to
Content
There is a difference between optparse and other deprecated module. Other modules are deprecated if they are too buggy or bad-designed to be fixed and there are stable standard or third-party modules that provides similar functionality. But looking on a number of open issues for argparse it seems that optparse is more stable and has less bugs than more powerful argparse.

Having experience with converting many modules from optparse to argparse or reviewing converting patches, I can say that not always the conversion can be done without loss. For example there is a difference in formatting descriptions.

I think that optparse should be supported in the stdlib for very long time. -1 for non-pending warning. Don’t have an opinion about pending warning.
History
Date User Action Args
2015-11-01 15:48:14serhiy.storchakasetrecipients: + serhiy.storchaka, r.david.murray, SilentGhost, martin.panter, matrixise, John Hagen
2015-11-01 15:48:14serhiy.storchakasetmessageid: <1446392894.13.0.000960147917143.issue25521@psf.upfronthosting.co.za>
2015-11-01 15:48:14serhiy.storchakalinkissue25521 messages
2015-11-01 15:48:14serhiy.storchakacreate