News for hackers. Stuff that matters.

A comment on Solving multi-core Python. Parent comment

Re:Solving multi-core Python by crdoconnor on Friday July 10, 2015 @12:59AM (#9862377)
I'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.

[ Parent | on HN ]
Re:Solving multi-core Python by logicchains on Friday July 10, 2015 @04:08AM (#9862798)
>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.

[ Parent | on HN ]
Re:Solving multi-core Python by easytiger on Friday July 10, 2015 @11:46AM (#9864590)
No, this is pretty easy in c. i think the python docs even apologise for it somewhere.
[ Parent | on HN ]