"Martin v. Löwis" martin at v.loewis.de
Mon Sep 28 06:09:53 CEST 2009

• Previous message: [Python-Dev] PEP 389: argparse - new command line parsing module
• Next message: [Python-Dev] PEP 389: argparse - new command line parsing module
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> If you think getopt and optparse should stick around in 3.X, why is
> that? If you think there are things that getopt and optparse do better
> than argparse, could you please give some examples?

I personally consider getopt superior to both optparse and argparse.
Those are terribly verbose in specifying arguments, whereas getopt's
sequence-of-letters is really nice and compact.

Regards,
Martin

---

• Previous message: [Python-Dev] PEP 389: argparse - new command line parsing module
• Next message: [Python-Dev] PEP 389: argparse - new command line parsing module
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list