Building nice command line interfaces - a look beyond the stdlib
Formal Metadata
| Title | Building nice command line interfaces - a look beyond the stdlib |
|
| Title of Series | |
| Part Number | 118 |
| Number of Parts | 173 |
| Author | |
| License | CC Attribution - NonCommercial - ShareAlike 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Bilbao, Euskadi, Spain |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Patrick Mühlbauer - Building nice command line interfaces - a look beyond the stdlib
One of the problems programmers are most often faced with is the parsing and validation of command-line arguments. If you're new to Python or programming in general, you might start by parsing sys.argv.
Or perhaps you might've already come across standard library solutions such as getopt, optparse or argparse in the official documentation.
While these modules are probably preferable to parsing sys.argv yourself, you might wonder if there are more satisfactory solutions outside of the standard library. Well, yes there are!
This talk will give you an overview of some popular alternatives to the standard library solutions (e.g. click, docopt and cliff), explain their basic concepts and differences and show how you can test your
CLIs. |
|
| Keywords | |