This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eli.bendersky
Recipients Aneesh, Peter.Caven, brian.curtin, eli.bendersky, georg.brandl, kbk, loewis, ned.deily, sunqiang, terry.reedy, tim.golden, vstinner
Date 2011-07-23.06:45:05
SpamBayes Score 4.7412163e-06
Marked as misclassified No
Message-id <1311403506.59.0.0480273416332.issue12540@psf.upfronthosting.co.za>
In-reply-to
Content
Am I missing something, or is there no explicit command to kill the subprocess on Windows in PyShell.py

The kill_subprocess method (which does get invoked) of ModifiedInterpreter is:

    def kill_subprocess(self):
        try:
            self.rpcclt.close()
        except AttributeError:  # no socket
            pass
        self.unix_terminate()
        self.tkconsole.executing = False
        self.rpcclt = None

The subprocess is started with:

    self.rpcpid = os.spawnv(os.P_NOWAIT, sys.executable, args)

Could it be that in earlier versions this ensured the subprocess exited with its parent, but this somehow got modified?

Note that the same code existed in PyShell.py for ages, so it's unlikely that the culprit is there.
History
Date User Action Args
2011-07-23 06:45:06eli.benderskysetrecipients: + eli.bendersky, loewis, georg.brandl, terry.reedy, kbk, vstinner, tim.golden, ned.deily, brian.curtin, sunqiang, Peter.Caven, Aneesh
2011-07-23 06:45:06eli.benderskysetmessageid: <1311403506.59.0.0480273416332.issue12540@psf.upfronthosting.co.za>
2011-07-23 06:45:05eli.benderskylinkissue12540 messages
2011-07-23 06:45:05eli.benderskycreate