This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jnoller
Recipients ac.james, jnoller
Date 2009-06-01.03:05:35
SpamBayes Score 1.0714535e-07
Marked as misclassified No
Message-id <1243825539.65.0.636829278521.issue6147@psf.upfronthosting.co.za>
In-reply-to
Content
Hey Alex; This isn't a bug, or a feature request. On win32, the way 
multiprocessing fakes a fork() is by creating a special subprocess which 
essentially imports and executes the function/process to be run, 
communication is handled through pickling and pipes.

For more information, see:
http://svn.python.org/view/python/trunk/Lib/multiprocessing/forking.py?
view=markup

Search for "# Windows" in that file, you'll see the basic process we use 
to "fork" on windows. Without a completely different implementation, 
this can not be changed. This probably will not change for some time, as 
such, I'm going to close this issue.
History
Date User Action Args
2009-06-01 03:05:40jnollersetrecipients: + jnoller, ac.james
2009-06-01 03:05:39jnollersetmessageid: <1243825539.65.0.636829278521.issue6147@psf.upfronthosting.co.za>
2009-06-01 03:05:38jnollerlinkissue6147 messages
2009-06-01 03:05:35jnollercreate