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 terry.reedy
Recipients IrvKalb, ned.deily, terry.reedy
Date 2020-07-28.22:18:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1595974738.0.0.0269033349459.issue41413@roundup.psfhosted.org>
In-reply-to
Content
IRv, please, please, snip the message you respond to when replying by email instead of with a browser.

I am guessing that you or someone installed python as root/admin and you are working as non-root. 

I will try to figure out why the change results in the 'running' box appearing twice instead of just once, and if a fix is possible that does not make this happen.  But I have noticed on other close issues that close is at least sometimes called more than once.  The shutdown system has multiple patches and is delicate to change, and not unittested, which would be non-trivial.  The peculiarily of this issue is that it is the initial idle process left running rather than the secondary user code execution process.
History
Date User Action Args
2020-07-28 22:18:58terry.reedysetrecipients: + terry.reedy, ned.deily, IrvKalb
2020-07-28 22:18:58terry.reedysetmessageid: <1595974738.0.0.0269033349459.issue41413@roundup.psfhosted.org>
2020-07-28 22:18:57terry.reedylinkissue41413 messages
2020-07-28 22:18:57terry.reedycreate