X-Received: by 10.236.14.99 with SMTP id c63mr7063675yhc.40.1402352513481; Mon, 09 Jun 2014 15:21:53 -0700 (PDT) X-Received: by 10.50.29.68 with SMTP id i4mr311703igh.0.1402352513382; Mon, 09 Jun 2014 15:21:53 -0700 (PDT) Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!hw13no5936257qab.0!news-out.google.com!qf4ni19596igc.0!nntp.google.com!h3no521284igd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.python Date: Mon, 9 Jun 2014 15:21:52 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.115.188.33; posting-account=yMP7kQoAAAAXsyJyvL-3qYVslbdYOSQP NNTP-Posting-Host: 76.115.188.33 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: os.startfile hanging onto the launched app, or my IDE? From: Josh English Injection-Date: Mon, 09 Jun 2014 22:21:53 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 2743 X-Received-Body-CRC: 549547903 Xref: csiph.com comp.lang.python:73062 On Saturday, June 7, 2014 1:24:43 PM UTC-7, Tim Golden wrote: > > I'm not 100% sure what your scenario is, but you can certainly help=20 > yourself and us by running the same test on the raw interpreter and then= =20 > under PyScripter to determine if the behaviour is to do with IDLE or=20 > with Python itself. >=20 > My half-guess is that PyScripter starts a new process to run your code,= =20 > possibly killing any pre-existing process first. That's if I've=20 > understood the situation you're describing. >=20 >=20 > Could you come back with a little more detail? Specifically: whether=20 > what you're seeing happens only from within PyScripter, or only not from= =20 > within PyScripter, or something else? >=20 I think you're right about PyScripter controlling the process. I don't run = scripts through the command line as a matter of practice.=20 But I just tried running my script through the command line, with Excel clo= sed, and it opened the Excel file just as I expected. Then I went back to t= he command line and ran it again, and it didn't close Excel. It gave me the= error I was expecting from zipfile not being able to access the file (beca= use it is currently open). I even left it open and ran another script that also creates and launches a= n Excel workbook, and it again did not close Excel. So this quirk is coming from PyScripter, which is a shame, because I don't = think it's under development, so it won't be fixed. Josh