Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document Windows interrupt event #244

Open
minrk opened this issue Mar 1, 2017 · 0 comments
Open

Document Windows interrupt event #244

minrk opened this issue Mar 1, 2017 · 0 comments

Comments

@minrk
Copy link
Member

minrk commented Mar 1, 2017

We don't send SIGINT to kernels on Windows, we send a Windows event identified by the JPY_INTERRUPT_EVENT env variable. This isn't documented, so it's likely that most kernels other than Python are not interruptible on Windows.

It might also be worth investigating if we can in fact switch back to sending a plain SIGINT, which would be simpler for kernels to handle. I don't recall why we added this event handler beyond "Windows signals are weird" because it is from long ago. It may have to do with the independent option, corresponding to CREATE_NEW_PROCESS_GROUP. I don't believe this option is used anymore.

cf JuliaLang/IJulia.jl#503 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants