I'm curious in how the Global Interpreter Lock in python actually works. If I have a c++ application launch four separate instances of a python script will they run in parallel on separate cores, or does the GIL go even deeper then just the single process that was launched and control all python process's regardless of the process that spawned it?
+10
A:
The GIL only affects threads within a single process. The multiprocessing module is in fact an alternative to threading that lets Python programs use multiple cores &c. Your scenario will easily allow use of multiple cores, too.
Alex Martelli
2009-06-14 04:09:11
You sure are helping me alot today. Thanks!
whatWhat
2009-06-14 04:11:18
You're most welcome!
Alex Martelli
2009-06-14 04:12:09
A "Plain Old Unix Pipeline" of Python applications is often a better design than multiple threads. A pipeline of processes avoids all GIL issues. It also avoids any potential thread-safety issues in any library you happen to be using. It's easy to create using the shell. The OS handles synchronization for you -- you just read from sys.stdin and write to sys.stdout.
S.Lott
2009-06-14 09:56:28
+2
A:
As Alex Martelli points out you can indeed avoid the GIL by running multiple processes, I just want to add and point out that the GIL is a limitation of the implementation (CPython) and not of Python in general, it's possible to implement Python without this limitation. Stackless Python comes to mind.
Merijn
2009-06-14 16:49:48