Re: Python : parsing the command line options using optparse

References	(2 earlier) <CACT3xuUGtsER0B3xwAB2CqQ5Zb=v72w8+DQkaYz681xeSeJ2CQ@mail.gmail.com> <lekj1t$v7n$1@ger.gmane.org> <CACT3xuXWBQC2s2XxE=Cav+RK78voPjbLA0cWSxL50ekktJZ2cg@mail.gmail.com> <mailman.7507.1393672393.18130.python-list@python.org> <5311c8b7$0$29985$c3e8da3$5496439d@news.astraweb.com>
Date	2014-03-01 17:47 +0530
Subject	Re: Python : parsing the command line options using optparse
From	Ganesh Pal <ganesh1pal@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.7511.1393676702.18130.python-list@python.org> (permalink)

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Sat, Mar 1, 2014 at 5:17 PM, Steven D'Aprano <
steve+comp.lang.python@pearwood.info> wrote:

>
> You should start new threads for new questions. The subject line here has
> nothing to do with the questions you ask.
>
>

Sure Steven  and thanks for replying  and  your suggestion for Question 2
 ( same as  Peter Otten ) worked and Iam closing this thread now  :)

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Python : parsing the command line options using optparse Ganesh Pal <ganesh1pal@gmail.com> - 2014-03-01 16:43 +0530
  Re: Python : parsing the command line options using optparse Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-03-01 11:47 +0000
    Re: Python : parsing the command line options using optparse Ganesh Pal <ganesh1pal@gmail.com> - 2014-03-01 17:47 +0530

csiph-web