Jump to content

  • Log In with Google      Sign In   
  • Create Account

Community Status Updates



Who, exactly, was the imbicile who thought that putting a library called "threading" and a class called "ThreadPoolExecutor" into a programming language which is completely incapable of multithreading? This is the kind of thing which leads to people with pitchforks and torches. Verdammt noch eins.
Sep 21 2015 03:25 AM
  • sloosecannon's Photo
    Java? Or something else. Initial Google searches seemed to indicate Java, which is (?) multithreaded?
    Sep 21 2015 08:01 AM
  • mmeier's Photo
    Python. It is one really big joke. Google Global Interpreter Lock. Basically: The Python interpreter cannot execute more than one python statement at the same time. Which makes multithreading completely impossible. I even understand why they did that - it makes the Python Interpreter implementation far (far far far) simpler and allows for a very simple garbage collection algorithm. But it also makes the language utterly unusable for anything one might wish to execute on several cores. Like, y...
    Sep 21 2015 09:07 AM
  • sloosecannon's Photo
    Ah, so it's concurrent, not parallel. That's... nice... or not....

    You could probably launch multiple Python processes via shell execs and fork. It would be absolutely horribly hacky, but I think that would work
    Sep 21 2015 10:13 AM