Hello,
I am writing a program that gets its parameters from a combination of
config file (using configparser) and command line arguments (using
argparse). Now I would also like the program to be able to _write_ a
configparser config file that contains only the parameters actually
given on the
On 15.05.2013 14:24, Roy Smith wrote:
In article ,
Henry Leyh wrote:
Is there a simple way to determine which
command line arguments were actually given on the commandline, i.e. does
argparse.ArgumentParser() know which of its namespace members were
actually hit during parse_args().
I
On 15.05.2013 15:00, Oscar Benjamin wrote:
On 15 May 2013 13:52, Henry Leyh wrote:
On 15.05.2013 14:24, Roy Smith wrote:
In article ,
Henry Leyh wrote:
Is there a simple way to determine which
command line arguments were actually given on the commandline, i.e. does
On 15.05.2013 16:08, Skip Montanaro wrote:
Yes, I was trying that and it sort of works with strings if I use something sufficiently improbable
like "__UNSELECTED__" as default. But it gets difficult with boolean or even number
arguments where you just may not have valid "improbable" defaults.
On 15.05.2013 17:29, Roy Smith wrote:
In article ,
Henry Leyh wrote:
On 15.05.2013 14:24, Roy Smith wrote:
In article ,
Henry Leyh wrote:
Is there a simple way to determine which
command line arguments were actually given on the commandline, i.e. does
argparse.ArgumentParser() know
On 16.05.2013 08:08, Jussi Piitulainen wrote:
Henry Leyh writes:
But now I would also like to be able to _write_ such a config file
FILE that can be read in a later run. And FILE should contain only
those arguments that were given on the command line.
Say, I tell argparse to look for
