4 ms·
multiprocessing can be fickle. In ipython, ctrl-c during a computation using multiprocessing results in general unhappiness, and will probably be followed by a
by ant6n 11y ago
multiprocessing can be fickle. In ipython, ctrl-c during a computation using multiprocessing results in general unhappiness, and will probably be followed by a 'killall python'
- vosper 11y agoOh, yeah - and this one! Much more so than the inconvenience I posted!
- crdoconnor 11y agoI've had this problem too, but after doing the (quite considerable) leg-work to fix it involving messing around with process groups and the ridiculous number of different types of signal, I'm more inclined to blame the horrible 30 year old UNIX APIs than python. I've had this signal handling problem in single process/single threaded code too, and in other languages. True, it would be nice if python layered on a nicer set of APIs to deal with the nastiness.
- logicchains 11y ago>I'm more inclined to blame the horrible 30 year old UNIX APIs than python. Datapoint: I encountered the same thing on Windows, having to use the Powershell equivalent of `killall python` to deal with it.
- easytiger 11y agoNo, this is pretty easy in c. i think the python docs even apologise for it somewhere.