Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #84918 > unrolled thread

Re: multiprocessing module backport from 3 to 2.7 - spawn feature

Started bySturla Molden <sturla.molden@gmail.com>
First post2015-01-30 21:15 +0000
Last post2015-01-30 21:15 +0000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: multiprocessing module backport from 3 to 2.7 - spawn feature Sturla Molden <sturla.molden@gmail.com> - 2015-01-30 21:15 +0000

#84918 — Re: multiprocessing module backport from 3 to 2.7 - spawn feature

FromSturla Molden <sturla.molden@gmail.com>
Date2015-01-30 21:15 +0000
SubjectRe: multiprocessing module backport from 3 to 2.7 - spawn feature
Message-ID<mailman.18321.1422652809.18130.python-list@python.org>
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.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web