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 brian.curtin
Recipients asvetlov, brian.curtin, pitrou, tim.golden
Date 2012-04-03.14:19:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333462800.02.0.13573522206.issue14484@psf.upfronthosting.co.za>
In-reply-to
Content
I can't find where we talked about this, maybe just IRC, but that's there (perhaps poorly) as a special case.

0 is 0, but signal.CTRL_C_EVENT is also 0. We try the signal version first then fall back to TerminateProcess.

I was just looking at this myself and it's not great. I actually wish we could change what signal.CTRL_C_EVENT means, or maybe add a flag to determine if the second parameter is supposed to be a return code or a signal? I'm open to anything.
History
Date User Action Args
2012-04-03 14:20:00brian.curtinsetrecipients: + brian.curtin, pitrou, tim.golden, asvetlov
2012-04-03 14:20:00brian.curtinsetmessageid: <1333462800.02.0.13573522206.issue14484@psf.upfronthosting.co.za>
2012-04-03 14:19:59brian.curtinlinkissue14484 messages
2012-04-03 14:19:59brian.curtincreate