Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #84774
| References | <CA+1Rt66fb5zFwKiBG=tkHzURfiYFX_xKo=XxUKvWO4CdySX0_Q@mail.gmail.com> |
|---|---|
| Date | 2015-01-28 12:06 -0600 |
| Subject | Re: multiprocessing module backport from 3 to 2.7 - spawn feature |
| From | Skip Montanaro <skip.montanaro@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.18228.1422468414.18130.python-list@python.org> (permalink) |
[Multipart message — attachments visible in raw view] - view raw
On Wed, Jan 28, 2015 at 7:07 AM, Andres Riancho <andres.riancho@gmail.com> wrote: > The feature I'm specially interested in is the ability to spawn > processes [1] instead of forking, which is not present in the 2.7 > version of the module. > Can you explain what you see as the difference between "spawn" and "fork" in this context? Are you using Windows perhaps? I don't know anything obviously different between the two terms on Unix systems. Skip
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: multiprocessing module backport from 3 to 2.7 - spawn feature Skip Montanaro <skip.montanaro@gmail.com> - 2015-01-28 12:06 -0600
csiph-web