RetroSearch Browse

Mon Sep 28 13:13:32 CEST 2009 · http://mail.python.org/pipermail/python-dev/2009-September/092200.html

Neal Becker wrote:
> If the plan is to migrate from optparse to argparse, this could be made a 
> bit easier.  If it weren't for the fact that some names are different in 
> argparse than optparse, I believe many optparse usages could port with no 
> change.
>   

The new names in argparse fit with the fact that argparse has a 
different 'rationale' than optparse. What about an optparse 
compatibility layer to make porting easier?

Although it can't cover the whole optparse API (as explained in the PEP) 
it could perhaps cover most 'normal' usage?

Michael

> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
>   

-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2009-September/092200.html below:

[Python-Dev] PEP 389: argparse - new command line parsing module