[issue35568] Expose the C raise() function in the signal module, for use on Windows

Change by Andrew Svetlov : -- components: +Library (Lib) resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35568] Expose the C raise() function in the signal module, for use on Windows

miss-islington added the comment: New changeset c24c6c2c9357da99961bf257078240529181daf3 by Miss Islington (bot) (Vladimir Matveev) in branch 'master': bpo-35568: add 'raise_signal' function (GH-11335) https://github.com/python/cpython/commit/c24c6c2c9357da99961bf257078240529181daf3

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Change by Vladimir Matveev : -- keywords: +patch, patch pull_requests: +10606, 10607 stage: -> patch review ___ Python tracker ___

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Change by Vladimir Matveev : -- keywords: +patch, patch, patch pull_requests: +10606, 10607, 10608 stage: -> patch review ___ Python tracker ___

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Change by Vladimir Matveev : -- keywords: +patch pull_requests: +10606 stage: -> patch review ___ Python tracker ___ ___

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Nathaniel Smith added the comment: I'd like to see it in 3.8, but don't know if I'll get to it, and it'd be a good onramp issue for someone who wants to get into cpython development. So, let's put the keyword on it for now, and see what happens... -- keywords: +easy (C)

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Steve Dower added the comment: That implementation will require some more of our usual macros around the call itself (for GIL and invalid values), and maybe clinicisation, as well as more through tests, which are probably going to be the hardest part. Nathaniel - were you planning to do

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Change by Vladimir Matveev : -- nosy: +v2m ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Nathaniel Smith added the comment: Vladimir Matveev pointed out that there's already a wrapper in _testcapimodule.c: https://github.com/python/cpython/blob/f06fba5965b4265c42291d10454f387b76111f26/Modules/_testcapimodule.c#L3862-L3879 So if we do add this to signalmodule.c, we can drop

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Nathaniel Smith added the comment: It probably doesn't matter too much either way, but almost all the signal-related wrappers are in signal. os.kill is the only exception AFAIK. -- ___ Python tracker

[issue35568] Expose the C raise() function in the signal module, for use on Windows

Steve Dower added the comment: Sounds fine to me. Any particular reason to put it in signal rather than os/posixmodule? If it's just to avoid treating os/posixmodule like a dumping ground for C89/POSIX APIs... well... too late :) I say keep dumping them there. But I don't have a strong

[issue35568] Expose the C raise() function in the signal module, for use on Windows

New submission from Nathaniel Smith : Suppose we want to test how a program responds to control-C. We'll want to write a test that delivers a SIGINT to our process at a time of our choosing, and then checks what happens. For example, asyncio and Trio both have tests like this, and Trio even