optparse: Why does this syntax work and not another?

[washu]

Hi,

I'm was going through the module help located on
http://docs.python.org/lib/optparse-store-action.html and I tried
modifying it a tiny bit and things don't work. If someone could tell me
what I'm doing wrong, I'd appreciate it.

The script that works (based on the code on the webpage) is:
#!/usr/bin/env python

import optparse, sys

parser = optparse.Option Parser()

parser.add_opti on("-f", action="store", type="string", dest="file_name ")
(options, args) = parser.parse_ar gs(sys.argv[1:])
print(options.f ile_name)

I call the script (optparse_test. py) in this fashion:
../optparse_test.p y -f foo.txt

And everything works. It will print foo.txt. Now, instead of doing the
parser = optparse.Option Parser() substitution, I spell everything out:

optparse.Option Parser().add_op tion( . . .)
(options, args) = optparse.Option Parser().parse_ args( . . . )

And the script stops with an error message of: "no such option: -f"

Anyone know why one syntax works and why the other doesn't?

[Peter Otten]

washu wrote:

optparse.Option Parser().add_op tion( . . .) Here you create an OptionParser instance and add one options
(options, args) = optparse.Option Parser().parse_ args( . . . )

Here you create a NEW OptionParser instance with no options and feed the
arguments to it.

Peter

[Anthony Baxter]

On Mon, 05 Jul 2004 06:36:46 GMT, washu <[e-mail] > wrote:

And everything works. It will print foo.txt. Now, instead of doing the
parser = optparse.Option Parser() substitution, I spell everything out:

optparse.Option Parser().add_op tion( . . .)
(options, args) = optparse.Option Parser().parse_ args( . . . )
And the script stops with an error message of: "no such option: -f"

Because your code is incorrect. The first of these two lines
creates and OptionParser() instance, and calls 'add_option()'
on it. It then throws away the newly created instance, as you
didn't assign it to anything.

[washu]

Thanks Anthony and Peter,

I didn't realize that optparse.Option Parser() was a class. It makes sense
now. Now that I think about it, it's obvious that it has to be a class.
Luckily, it gave me an excuse to down a couple of Guinness's.