News for hackers. Stuff that matters.
Re:The Python GIL Visualized by scott_s on Tuesday January 05, 2010 @02:01PM (#1032962)
I agree with you, but in practice, there won't be as much memory replication as you assume. Linux (and I assume most modern OSes) implement copy-on-write: no data is copied until a write occurs. So as long as the separate process only read that large data set, that large data set should exist in memory only once.
Re:The Python GIL Visualized by FooBarWidget on Tuesday January 05, 2010 @04:35PM (#1033443)
Exception multiprocessing does not use fork() (without exec()) because it has to be compatible with Windows.
Re:The Python GIL Visualized by rbanffy on Tuesday January 05, 2010 @06:39PM (#1033708)
Like I use to say: that's Microsoft holding everybody back. ;-)

Now, seriously, can we implement a better multiprocessing module for those with modern OSs and leave a less functional one (one that will raise a LesserOSError when certain functionality is invoked)?

Re:The Python GIL Visualized by jnoller on Tuesday January 05, 2010 @10:06PM (#1034047)
Incorrect; On linux and OS/X it uses fork. On windows it uses a best-effort clone.