Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #84918
| From | Sturla Molden <sturla.molden@gmail.com> |
|---|---|
| Subject | Re: multiprocessing module backport from 3 to 2.7 - spawn feature |
| Date | 2015-01-30 21:15 +0000 |
| References | <CA+1Rt66fb5zFwKiBG=tkHzURfiYFX_xKo=XxUKvWO4CdySX0_Q@mail.gmail.com> <CANc-5UyZZNkTjrVUt1M2zAUCeJGr_RffXcO_E4FiY5gZhSOD1A@mail.gmail.com> <CA+1Rt67KWpmqw_iLfu+0qYs9QGRvXjPA76FhJQ4mpWpOtz6eVA@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.18321.1422652809.18130.python-list@python.org> (permalink) |
Andres Riancho <andres.riancho@gmail.com> wrote: > Spawn, and I took that from the multiprocessing 3 documentation, will > create a new process without using fork(). > This means that no memory > is shared between the MainProcess and the spawn'ed sub-process created > by multiprocessing. If you memory map a segment with MAP_SHARED it will be shared, even after a spawn. File descriptors are also shared.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: multiprocessing module backport from 3 to 2.7 - spawn feature Sturla Molden <sturla.molden@gmail.com> - 2015-01-30 21:15 +0000
csiph-web