Migratingoptparse code toargparse

Theargparse module offers several higher level features not nativelyprovided by theoptparse module, including:

  • Handling positional arguments.

  • Supporting subcommands.

  • Allowing alternative option prefixes like+ and/.

  • Handling zero-or-more and one-or-more style arguments.

  • Producing more informative usage messages.

  • Providing a much simpler interface for customtype andaction.

Originally, theargparse module attempted to maintain compatibilitywithoptparse. However, the fundamental design differences betweensupporting declarative command line option processing (while leaving positionalargument processing to application code), and supporting both named optionsand positional arguments in the declarative interface mean that theAPI has diverged from that ofoptparse over time.

As described inChoosing an argument parsing library, applications that arecurrently usingoptparse and are happy with the way it works canjust continue to useoptparse.

Application developers that are considering migrating should also reviewthe list of intrinsic behavioural differences described in that sectionbefore deciding whether or not migration is desirable.

For applications that do choose to migrate fromoptparse toargparse,the following suggestions should be helpful: