Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=dblKQQ8q14hDvTE5+bYbkBuBlg00AhRFyxfCq00jh9lHHcko5XEMsFmRCU1aw9OeXW SLXwZqbtUB0En5EPwv+DzR0ckjIUCMNRAzdLwODHPcbrhKWR/sDd46yC298Nls09Qfld 4vK7YRs9n7qIznsVI/8pWIuMYMdxaGEaFRa6I=
MIME-Version: 1.0
In-Reply-To: <BANLkTin7fq7ybKq94ZUs-7X8dLu7_UFnrQ@mail.gmail.com>
References: <BANLkTikr8fu1sDrfu2a-wyEN_KpVVNCdew@mail.gmail.com> <BANLkTik_ZLvgUVuttiGKQshLmnkU_Mvk+g@mail.gmail.com> <BANLkTin7fq7ybKq94ZUs-7X8dLu7_UFnrQ@mail.gmail.com>
Date: Wed, 11 May 2011 18:46:36 +1000
Subject: Re: NewBie Doubt in Python Thread Programming
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.1396.1305103600.9059.python-list@python.org>
Lines: 62
NNTP-Posting-Host: 82.94.164.166
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:5099

I'm responding to this on-list on the assumption that this wasn't
meant to be private; apologies if you didn't intend for this to be the
case!

On Wed, May 11, 2011 at 6:38 PM, vijay swaminathan <swavijay@gmail.com> wro=
te:
> so If i understand correctly, once the run method of the thread is execut=
ed,
> the thread is no more alive.

Once run() finishes executing, the thread dies.

> Actually, I'm trying to invoke a command prompt to run some script and as
> long as the script runs on the command prompt, I would like to have the
> thread alive. But according to your statement, the thread would die off
> after invoking the command prompt. is there a way to keep the thread acti=
ve
> till I manually close the command prompt?

That depends on how the "invoke command prompt" function works.

> A snippet of the code written is:
> # Thread definition
> class RunMonitor(QThread):
> =A0=A0=A0 def __init__(self, parent=3DNone):
> =A0=A0=A0=A0=A0=A0=A0 QThread.__init__(self)
> =A0=A0=A0 def run(self):
> =A0=A0=A0=A0=A0=A0=A0 print 'Invoking Command Prompt..........'
> =A0=A0=A0=A0=A0=A0=A0 subprocess.call(["start", "/DC:\\Scripts",
> "scripts_to_execute.bat"], shell=3DTrue)
>
> =A0def sendData(self):
>
> =A0=A0=A0=A0=A0=A0=A0 if self.run_timer:
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 run_monitor_object =3D RunMonitor()
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 print 'Starting the thread...........'
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 run_monitor_object.start()
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 self.run_timer =3D False
>
> =A0=A0=A0=A0=A0=A0=A0 if run_monitor_object.isAlive():
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 print 'Thread Alive...'
> =A0=A0=A0=A0=A0=A0=A0 else:
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 print 'Thread is Dead....'
>

subprocess.call() will return immediately, so this won't work. But if
you use os.system() instead, then it should do as you intend.

> to check the status of the thread repeatedly I have the QTimer which woul=
d
> call the self.sendData() for every minute.
>
> =A0=A0=A0=A0=A0=A0=A0 self.timer =3D QTimer()
> =A0=A0=A0=A0=A0=A0=A0 self.timer.connect(self.timer, SIGNAL("timeout()"),=
self.sendData)
> =A0=A0=A0=A0=A0=A0=A0 self.timer.start(1000)

I'm not really sure what your overall goal is. Can you explain more of
your high-level intentions for this program? There may be a much
easier way to accomplish it.

Chris Angelico