Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    That first statement is incorrect. It does use multiple cores. Only one at the time can get the GIL. Commented Jul 25, 2011 at 19:55
  • Ah, I was missing a word. Fixed. Commented Jul 25, 2011 at 19:57
  • 5
    You miss the point. It is not the threading library itself that prevents it. It uses the pthread library, which can use all cores. This would implicate that one can fix the threading library and the problem is solved. But the problem is much deeper than that. Commented Jul 25, 2011 at 20:00
  • 2
    His statement however is correct -- he doesn't say it couldn't use multiple cores, he said it doesn't. Commented Jul 25, 2011 at 20:05
  • 1
    @Ikke: He refers to the Python threading library, not the underlying implementation (about which we need not know anything, and which is not necessarily using the POSIX threading API -- it certainly doesn't use it on Windows!). Commented Jul 25, 2011 at 20:05