Skip to content

Commit a5acafc

Browse files
committed
Mention KeyboardInterrupt does not work [ci skip]
1 parent db2c7f0 commit a5acafc

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -296,6 +296,22 @@ disk space than the similar hack for Julia 0.6.
296296
For the update on this problem, see:
297297
https://github.com/JuliaLang/julia/issues/28518
298298

299+
### <kbd>Ctrl-C</kbd> / KeyboardInterrupt support / SIGINT handler
300+
301+
Currently, initializing PyJulia (e.g., by `from julia import Main`)
302+
disables `KeyboardInterrupt` handling in the Python process. If you
303+
are using normal `python` interpreter, it means that canceling the
304+
input by <kbd>Ctrl-C</kbd> does not work and repeatedly providing
305+
<kbd>Ctrl-C</kbd> kills the whole Python process with the error
306+
message `WARNING: Force throwing a SIGINT`. Using IPython 7.0 or
307+
above is recommended to avoid such accidental shutdown.
308+
309+
It also means that there is no safe way to cancel long-running
310+
computations or I/O at the moment. Sending SIGINT with
311+
<kbd>Ctrl-C</kbd> will terminate the whole Python process.
312+
313+
For the update on this problem, see:
314+
https://github.com/JuliaPy/pyjulia/issues/211
299315

300316
Testing
301317
-------

0 commit comments

Comments
 (0)