Message108676
| Author |
r.david.murray |
| Recipients |
bethard, eric.smith, georg.brandl, iElectric, r.david.murray |
| Date |
2010年06月26日.01:35:24 |
| SpamBayes Score |
0.0013622204 |
| Marked as misclassified |
No |
| Message-id |
<1277516126.84.0.307686404039.issue9077@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Optparse left you to parse the arguments:
>>> import optparse
>>> p = optparse.OptionParser()
>>> p.add_option('--test', action="store_true")
<Option at 0x96521bc: --test>
>>> p.parse_args(['--test', 'foo', '--', 'foo2'])
(<Values at 0x97020a4: {'test': True}>, ['foo', 'foo2'])
As you can see, the 'foo' before the '--' is one of the returned arguments. So argparse is behaving exactly the same way as optparse in this instance, except that, as I said, it is *parsing* the arguments. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年06月26日 01:35:27 | r.david.murray | set | recipients:
+ r.david.murray, georg.brandl, bethard, eric.smith, iElectric |
| 2010年06月26日 01:35:26 | r.david.murray | set | messageid: <1277516126.84.0.307686404039.issue9077@psf.upfronthosting.co.za> |
| 2010年06月26日 01:35:24 | r.david.murray | link | issue9077 messages |
| 2010年06月26日 01:35:24 | r.david.murray | create |
|