[Python-Dev] PEP 389: argparse - new command line parsing module
Robert Kern
robert.kern at gmail.com
Wed Sep 30 18:44:23 CEST 2009
More information about the Python-Dev mailing list
Wed Sep 30 18:44:23 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 ]
On 2009-09-29 18:38 PM, Steven Bethard wrote: > I don't really use GUI libraries, so I wouldn't be able to come up > with such an example. I'd also rather not make API changes based on > speculative use cases, so before I spend time documenting these > things, I'd really like to hear from someone who has already, say, > used getopt or optparse in conjunction with a GUI library, and what > feedback they have about that. I use argparse (and previously optparse) frequently to handle the command line arguments of GUI apps. I tend to use them in the same way as CLI programs, though, since I usually only use command line arguments when starting the GUIs from the terminal. I am blissfully unaware of the problems Paul mentioned about Windows GUI-mode programs. I'm not sure what would make a program "GUI-mode" or not. Certainly, I have written Python programs that use wxPython and PyQt on Windows that print to stdout/stderr, and they appear to work fine. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
- 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